Category Archives: Automation
Generic Automation Rules for Project Tasks
It was already possible to create automation rules for specific project tasks, and to update the phase of a project task. Now it is also possible to create generic automation rules on project tasks. This makes it possible to automatically assign a project task to a person, team, or agile board, or to add a […]
Project Assessment Fields Accessible by Automation Rules
Several fields of project records that could previously not be accessed by automation rules are now available for automation. This concerns mainly the financial information of a project: effort value cost_of_effort cost_of purchases total_cost budget_allocated This allows an organization, for example, to make a first assessment of a candidate project via a request template. Once […]
Update Customer Representatives with Automation Rules
Since the previous release the customer representative(s) can see all requests and dashboards related to an SLA in Xurrent Self Service. It is now also possible to update customer representatives in an SLA using automation rules. Service providers can use this to automatically add (or remove) persons (such as account managers of a customer) as […]
Access Child Service Instances with Automation Rules
Automation rules can now access the child service instances of a service instance. This makes it possible for service providers to automatically assign a request to a team that is responsible for the child service instance, for example.
Access Workflows with Project Task Automation Rules
From a workflow it is possible to start a project. It is now also possible for an automation rule to access the workflow that started the project. One use case would be for an organization to create an automation rule that completes the workflow that started a project, as soon as that project is completed. […]
Automation Rules Can Access CI Creation Date
It is now possible to access the creation date of a configuration item with automation rules. This can be useful if certain checks need to be executed on configuration items depending on their age, as in the example below.
Import Source for Automation Rules per Type
When importing records into Xurrent, the Source and SourceID fields are checked to see if a record already exists. This is also true when importing automation rules, which is done to transfer them between Xurrent environments, for example. When exporting automation rules, multiple export files are created; one for each automation rule type (request, request […]
Problem Analysis Target field in Automation Rules
In problem records, the Analysis target field is used to specify when the current assignee needs to have completed the root cause analysis of the problem. It is now possible to check and update the value of this field using an automation rule, as can be seen in the screenshot below.
Automation Trail Shows Originating Account
Especially for enterprise organizations and MSPs, executed automation rules can originate in various accounts. For people tasked with troubleshooting, it can sometimes be challenging to identify the account where the rule was defined. When an automation rule is executed in a different account than the one a record is viewed from, and the user has […]