v.venkateswarlu wrote:
Hi,
This can be achieved by Spel code customization.
Here is the sample of Spel code to modify the status of the newly created ticket.
MODIFY cr status ON_NEW DEFAULT ACK; // assigning default as acknowledged.
but here i am not sure how to validate the group and assignee are updated.
waiting for some body to get in and provide a solution.
Thanks,
Venkat
Thanks Venkat,
Good solution. Hopefully Swapnil can write the check to see that the two fields aren't null.
SPL is best for this, but is an unsupported customisation.
The test scenario should confirm that the Status is not accidentally set back to "Acknowledged" at other times in the ticket lifecycle.
The other way to go would be a Conditional Macro and Event that runs periodically and then updates the Status. It's best not to overload the Animator with these types of regular checks though, that are likely only to be met once, if it can be avoided.
(Maybe attached to "Initial" - or is that too soon in the process flow?)
A final thought is that it is not all bad to have an Analyst set the first Status on a ticket manually. It gives confidence that a human has looked at the ticket.
Swapnil - let us know how you go.
Anyone else - feel free to comment, especially if you run something similar.
Thanks, Kyle_R.