Histórico da Página

Control attachment security
When configured, it determines that there will be you can control over the viewing and manipulation handling of the documents attached to the process requests, meaning it is possible to ; that is, you can define which groups, roles, and individuals will have specific permissions on the attachments. To configure, simply click on Configure attachment security. See the Click here to view step-by-step by clicking hereinstructions.

Update attachment
When activated, it determines that the attachments of the request that are published in the Documents resource will be are updated in the request whenever they are updated in Documents. If not activated, even if you update the attachment is updated in Documents, in the request it will remain remains in the version that was there when it was it originally had when added. This applies to attachments added to the request from the Documents resource and to attachments added to the request and published in Documents through development on the platform.

Activate process
When activated, it determines that the process is available for use in the Start request resource, meaning it is you can already possible to open requests for this process. The version made available for use is the last one that was published. By default, this option is activated. However, if it is deactivated, as long as it is not activated you do not activate it again, the process will is not be available for use.

Make public
When activated, it determines that anyone can consult the requests for this process. If not activated, the requests can only be consulted by the requester, by those who participated in the process, or by the process managers, or the requester can consult the requests.

Available for mobile
When activated, it determines that the process is available for use in the mobile application of the platform, meaning it is possible to you can open and manage requests for this process through the application.

Confirm password
When activated, it determines that all steps of the process will require the password of the person executing it, aiming to reaffirm the presence of each person in the execution of the step.

The available options are:

• By form field: when selected, it determines that only the person filling in a field of the request form will receive receives the permissions assigned to the documents attached to the process.

• By group: when selected, it determines that only the people from a specific group will receive the permissions assigned to the documents attached to the process requests.

• By role: when selected, it determines that only the people who hold a specific role will receive the permissions assigned to the documents attached to the process requests.

• By person: when selected, it determines that only a specific person will receive receives the permissions assigned to the documents attached to the process requests.

• By anyone: when selected, it determines that anyone will receive receives the permissions assigned to the documents attached to the process requests.

In this tab, you can create specific properties for this process. These , which uses these advanced properties are used to provide data that can be requested during the process events, through the dataset advancedProcessProperties or through coding.

Attribute
Name for identifying the property.

Value
Value that will to be defined for the property.

To cancel the inclusion addition of the property, just click on Cancel.

You can edit the added property by clicking on Edit , changing the information, and clicking on Saveagain.

To remove an added property, just click on Remove.

To cancel the changes made, simply click on Cancel instead of saving.

When saving the draft, you save the latest changes you made to the process that have you did not yet been published are saved publish in the version that is being editedyou are editing, but it is they are still not available for use when opening requests. It is necessary You need to publish the process with the changes you have made for them to be considered able to use them in the next requests that are openedyou open.

Up The system allows up to two hundred (200) characters are allowed in the description.

If it is To the first version, it is interesting to include you should add an overview of the process, with information such as its objective, what it allows to request, its target audience, among others.

If it is To a new version, it is interesting to detail what changes were you should detail the changes you've made, as they will be listed in the process history will list them later.

By clicking Click this option , to automatically perform a consistency analysis of the process configurations is automatically performed. If all the necessary required information and configurations are correct, the process is published. Otherwise, the system displays a message is displayed informing notifying about the existing inconsistencies that you need to be adjusted for to adjust in order to publish the process to be published. To return to the process and correct the inconsistencies, just click on Return to process and correct.

Once published, the new version of the process containing the latest changes made is released for use. Ongoing requests continue with the configurations of the old version. Only new newly opened requests opened will have the configurations of the new version of the process.

After publishing the process is published, in the displayed confirmation message, you can click on Return to editing – to go back to the process and continue editing it – or Start request – to open a request in a new tab.

This documentation is valid from the Voyager update (2.0) update onwards. If you are using a previous update, it may contain information different from what you see on your platform.