Jump to content

Recommended Posts

Posted

Hi,


I have been trialling an autotask to update the logging category to replicate the category of the request upon closure.

 

I have tried each of the variables but none seem to work? Anyone have any ideas on how to make this work? This will be part of a BP - just using the autotask to test out. The idea is that when a request is resolved, it will update the logging category to replicate the closure category.

 

I've checked that the category codes match for the codes on my example request with whats in the profile admin section too

coding-test.draft.bpm.txt

Posted

Hi @James Ainsworth

The entity is set to Requests

The Update Coding node is (I think) set up with the correct task. I'm trying to update the request category to replicate the closure category once the closure category has been set 😕

  • 2 weeks later...
Posted

Hi Will,

After an investigation, the development team explained to me what was happening.  The Request and Closure categories are two separate category profile trees.  An ID from a closure category will not match the ID from a request category.

I'm interested in understanding the use case for automatically setting the request category and the closure category to be the same.  Typically, these are used for two distinct sets of criteria.  The request category is typically used to describe the area or function that is impacted and the closure category is used to describe how it was closed.

Request Category = email, server, hardware, software, documentation, etc.

Closure Category = update, replacement, training, patch, setting, configuration, etc.

Using the categories in this way helps provide more statistics.  

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...