Perhaps the simplest way would be, when starting the approval, to send an email containing the list of approvers.
Hi Alan, Unfortunately this wont work for us as we are not using the state actions for hold/off hold. We are using a custom action which is triggering on hold/off hold via the action processor. We were hoping to have a search parameter to search where SLA Stop Clock is triggered or not. If there is a custom action to call the clock action, why not use this action as a filter in the 'action' tab?Another way would be to change the clock actions to user status: stop/star clock is to use as already informed as a suggestion.
1- Criar variavel adicional do processo anexado: ["AV_ATTACHED_PROCESS_SC"] = "event.attachedProcess.shortCode", -- Attached process. only valid for parent event (e.g. not tasks) https://wiki.axiossystems.com/assyst11-4Wiki/index.php/Integrations:Action_Processor_Manual#Using_additional_variables_with_Event_Data2- Criar entrada do action a ser iniciado quando o evento principal iniciar a ação de decisão ex.: { [[ ATUALIZA CAMPO ADICIONAL ], [[ ACT_TYPE_SC == "SC_STAGE_DECISICION" and AV_ATTACHED_PROCESS_SC == "SC_PROCESS" ]], [["C:\Axios\Software\SmartMail\send_email.exe" -config "C:\Axios\Automations\SmartMail\Logic\test_uptdate.conf" ACT_REG_ID=$ACT_REG_ID EVENT_ID=$EVENT_ID ]], "continue" }, https://wiki.axiossystems.com/assyst11-4Wiki/index.php/Integrations:Action_Processor_Manual3- criar select no banco para retornar o usuario atribuido na mudança https://wiki.axiossystems.com/assyst11-4Wiki/index.php/Integrations:Smar
personally I am not in favor of the requester knowing who the approver is because the process must guarantee that the request will be met regardless of the approver, otherwise the user feels entitled to charge the approver directly. But for the scenario presented, the ideal is that in the main call there should be a field to point out the approver (if he is already known), or this field can be fed by the service desk in one of the steps of the process. Another more complex way would be to use the decision step record as a trigger for the action processor to retrieve the name of the approver and, via rest_update, update the field of the main call
On the 1st error screen, the item and category are not displayed. Is the Order registered via the service catalog or is the data informed during registration? it would be interesting to print the steps of the registry.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
