Processes: Process Detail

The Process Detail tab of any process defined within Integrify lets you edit basic process settings, copy a process, make a version of an existing process, export a process or delete a process entirely.

In this section we will discuss:

  • Process Settings
  • Allowing Ad-hoc Related Requests
  • Publish Status
  • Copying/Versioning a Process
  • Exporting a Process
  • Removing a Process
  • Links/API Options

Process Settings

The settings area contains process-level settings that may be edited and updated at any time. Most of the information is informational, however, a few settings will impact the location of the process or the visibility of the process to the end user.

 

Any setting that is in Bold text is available to be edited. To edit any options from the Settings List, simply click on the pencil icon in the Edit column in the grid for the particular setting.

In the example above, the Name setting has been selected and the process name may be changed.

The following table is a list and description of all available settings:

Setting Editable Description
ID No Unique id of the process.
Name Yes This is the process name as displayed to your end user. Names are not unique and may be duplicated in the system if necessary.
Version No Current version of your process. This value increments for each version you create of the same process.
Publish Status Yes Integrify contains 4 distinct publish status: Development, Testing, Production and Inactive.
Category Yes The category where the process is stored and where an end user will initiate the process under the Start Request menu.
Description Yes Basic description of your process. Visible to the end user when starting a request.
Style Template Yes The Style Template impacts how the Request Detail is displayed to the end user. The style template selected here becomes the default style template for all tasks that are created for the process. Task style template selection may override the default selected here.
Objective Yes Basic objective information about the process.
Information URL Yes A link that may be added to an online help system concerning the process.
Attachments Yes A Process Administrator may attachment additional documentation about the process such as a Visio diagram, Word Document, PDF, etc. This is accessible to the end user.
Allow Comments Yes Allows you to toggle whether end users are allowed to enter comments for requests submitted against this process.
Allow Ad-hoc Related Requests Yes Allows end users to launch ad-hoc related requests.  This will display a Related Requests section within the Request Detail section of the process for any ad-hoc related requests that are launched by a user. (See screenshot examples below)
Allow Request to be Copied Yes Allows end users to copy their requests.  This will display a Copy Request button above the Summary information on the Request Detail tab of a request. Note: The process must have the first task be a form task.  The copy a request feature will present the user with the first form task prefilled with data from the previously submitted form task.
Allow Request to be Cancelled Yes Allows end users to cancel their requests.  This will display a Cancel Requestbutton above the Summary information on the Request Detail tab of a request.
Visible to users Starting New Request Yes This flag can hide the request from an end user from initiating this process manually. This setting is most typically used when a process always needs to be started programmatically via Integrify’s Services API. This could also be used for a child process that you don't want displayed when users start requests.
Visible to Mobile App Users Starting New Request Yes This flag will make the process available for users to start a request from the Integrify mobile app.
Skip Start Request Entry Yes By default, the setting is 'No' which presents a pop-up window for a user to either rename a request or select another user to submit the request on behalf of. By selecting 'Yes', the initial task will be triggered when the user selects the process to start, bypassing the pop-up window.
Hide Flow Tab in Requests/Tasks Yes By default, the setting is 'No' which presents the Flow View tab to users when reviewing a request or task. By selecting 'Yes', the Flow View tab is not presented.
Process Attributes Yes By default, the setting is 'No'. Should you want the process to be initiated via an email by using the Email Monitor service, select 'Yes'.
This process should be completed in... Yes Allows you to set the time interval that the process should be completed in by minutes, hours or days.  Often used as data for reports that measure service level agreements (if processes are being completed on time).
Created No Date process was created.
Last Modified No Date process was last modified.
SID No Integrify's unique identifier for the process.
Permissions No Current permission level(s) for the process.
Advanced Settings Yes Allows you to optimize the process for mulitple loopbacks.

 

Allowing Ad-hoc Related Requests

By checking the value to 'Yes' for 'Allow Ad-hoc Related Requests' in the Process Settings above, you will allow the user that is looking a submitted request the ability to relate it to another existing request in the system.

Users can choose to launch a request as a child to the request that is being viewed or choose an existing request as a parent of the request being viewed.

Screenshots of how a user can launch an ad-hoc related request when the process allows for it:

 

Screenshot of the Request Detail of a process that has an ad-hoc related request:

 

Publish Status

 Integrify has been designed so that a single Integrify installation may act as a development, testing, and production environment.  This is accomplished through a combination of Publish Statuses and system security.


There are four distinct Publish Statuses that may be applied to a process which follow the typical life cycle of a process

  • Development: used during initial process configuration, development,  and unit testing.
  • Testing: used after unit testing and for a wider audience other than the process developer.
  • Production:  used when the process is live and available for your end users.
  • Inactive:  used when a process is decommissioned and a new version of a process has been published to Production.  The Inactive status allows existing requests against that process definition to complete normally but no new requests may be started against it.

In a typically Integrify installation, security is set-up so your end users can start/view processes that have a Publish Status of Production.  By integrating the Publish Status of a given process with system security it makes it possible to have that single Integrify installation to act as your development, testing, and production environment.

For example, when a new process is created, the default Publish Status for that new process is set to Development.  If your end users were to navigate to the Category that contains the new process they would never see the process.  The Integrify system security filters out processes the end user can see by evaluating the Publish Statuses of processes in any given category(s).   

Similarly when the development cycle for the new process is complete and you wish to perform QA testing with a larger group of users, you would change the Publish Status to Testing.   Again, your average end user would be restricted from starting this process as he/she does not have access to processes with a Publish Status of Testing.    But, it is possible to create secondary role(s) in Integrify such that certain users could see this process if the role they are in can see processes with a Publish Status of Testing.

Finally, after testing is complete and you move the Publish Status to Production, then you end users would be able execute the process when they log into Integrify.

Copying/Versioning a Process

There is a subtle distinct between the Copy Process and the Version Process options available on the Process Detail tab.

    • Copy Process:  will copy the entire process definition (tasks, business rules, recipients, etc) and allocate a new unique process ID value.  When you select Copy Process, you will notice that the ID value has incremented and the Name of the process will have changed to Copy of {Your Process Name}.  The process will remain in the same category but you may change any of the Process Detail options at this time.

 

  • Version Process:  will copy the entire process definition (task, business rules, recipients, etc), increment the Version number, and change the Publish Status to Development but leave the unique process ID value the same.  When you select Version Process, you will notice that the Version value has incremented and the Name of the process will have changed to Version of {Your Process Name}.  The process will remain in the same category but you may change any of the Process Detail options at this time.


You use the Copy Process option when you would like to create a new process that is similar to another already designed but only need to make small changes.

You use the Version Process option when you need to make changes to an existing process that is currently in production and being used.

 

Exporting a Process

The Export Process option exports your entire process to a standard process definition file which may be imported into another instance of Integrify.


If you have multiple installations of Integrify installed at your location, it is possible to have a stand-alone development, test, and production environments and move a process seamlessly between those environments.  The only exceptions being that any attached files to the process, and any task type that requires templates (PDF and Excel task types) are not included in a process export.  Those templates and attachments will need to be added to the imported process, and the task will need to be reconfigured.

When you select Export Process, you will be presented with a dialog to save the exported process definition file to your desktop.

 

Removing a Process

To completely remove a process from Integrify by pressing the Delete Process button at the top of the Process Detail tab.   By removing a process you are effectively removing the entire process definition and any outstanding requests that may be executing against the process definition will be impacted.

Note:  Do Not Remove a process unless you are absolutely sure that no outstanding requests are pending against that process.  You cannot un-delete a process once it has been removed.

 

Links/API Options

For customers that have the Integrify API, the Administrators can select the Links/API Options button to see how to link to the process.  This allows for the process to be linked to from external webpages and/or within an Integrify HTML Panel widget.

Simply copy and paste any of the options.

Mike -

Comments

Powered by Zendesk