Configure the advanced properties of a process

  1. On the Extended Properties page, click the Advanced tab.
  2. On the Allocation Algorithm list, select one of the algorithm options for allocating work to the resources. (Default: First Found)
  3. Select the required Thread Pool to associate with the map. See Add a thread pool.
  4. To release the process maps within your organization using the OnRelease event, consume the process in the On Release Process box. The selected process is created when the current business process is released.

    To handle the release, you can:

    • Create a new process, such as Approve Loan Application Release process map.

    • Add activities to the event handling map to take whatever steps are required before the map can be released, such as notifying someone or getting approval.

    • The event handling map must release the map after the release business logic is completed.

      Note Use an API call to the ReleaseProcess method available in ProcessService SDK.

  5. To allow the process to be synchronous so that it only has automatic activities, and does not have any manual activities, click Yes for Synchronous. (Default: No)
  6. Continuous looping in a synchronous job or business rule can cause high workload on the TotalAgility server. To prevent this, click Yes for Maximum Loop Count (default: No) and set the number of times an activity can be executed in a synchronous job or business rule. (Default: 1000)

    When the loop count reaches the set limit, the job is suspended at runtime.

    Note
    • This setting is only available for a synchronous map.

    • The loop count set at the process level takes precedence over the loop count set at the system level. See Work process.

    • If you do not specify a loop count at the process level, the loop count set at the system level is considered.

  7. Consume the .NET Assemblies to associate with the process.

    Note the following:

    • When you export a process, the .NET assemblies associated with the process gets exported.

    • When you import a process from a version previous to TotalAgility 7.0 then all the available .NET assemblies get imported. However, you can configure the assemblies that are needed.

    • When you view a system map, the process is updated with the associated .NET assemblies.

  8. To make a case fragment map compatible with all case versions, click Yes for Compatible with all Case Def Versions.

    This means that a job can be created on a case that is running on an older version of a case. This property is only available for a case fragment map.

  9. Configure the Case Completion property. See Configure case completion.
  10. In the Data group, configure the following properties:
    1. Include in Analytics: If set to Yes, ensures that the data related to jobs for this process is picked up by Kofax Analytics for TotalAgility (KAFTA) reporting. Additionally, the documents and page counts are recorded for the process activities in TotalAgility that can be used by KAFTA reporting. (Default: No)
    2. Click Yes to Track Variable Changes. (Default: No)
    3. Click Yes for Use Variable Prefix to enable variable prefixing for ease in identifying whether the variable is a process, case or server variable. (Default: No)
      • A process variable is prefixed with p, for example, p_SessionId.

      • A case variable is prefixed with c, for example, c_SessionId.

      • A server variable is prefixed with s, for example, s_SessionId.

    4. Record History: By default records the history of data, such as an activity taken and completed.
    5. Retention Policy: To configure the retention period for completed or terminated jobs and cases of the process, select either option:
      • Indefinitely (default): Retains the process permanently.
      • Custom: Retains the process for a specific period. Enter the number of Years, Months and Days. (Default: 1 year, Minimum value: 1 day)
      The jobs are automatically deleted once the retention period is over.
      Note Deleting is a non-recoverable action.
  11. Configure the retention period for a process. See Configure the retention policy for a process.
  12. Configure Virtual Folders. See Create virtual folders.
  13. In the Process Active Period group, set the time frame (Active From and Active Until) to restrict the process to be active for a specific duration. If you set the process active period, the process expires as soon as the active period is over. For example, a garment retailer decides to implement a discount scheme for Christmas and creates a process map that begins at the start of the season and expires at the end the season.
    Note By default, the Process Active Period is Not Specified. This means that a process remains active.
  14. Add Help Text (information) about the process as Plain Text or as a URL to a web page.
  15. Click Save.