lee mcdermott Posted April 7, 2022 Posted April 7, 2022 One of our changes has closed itself with the following? An ideas what this means and why it may have done this? I've never seen this before. thanks lee
Victor Posted April 7, 2022 Posted April 7, 2022 @lee mcdermott in essence, any action in Hornbill is tied to a user, it will execute in the context of a user. Some actions that are not specifically performed by one of your analysts, for example automated actions performed by a business process independently of an analyst performing an action (e.g. a suspended node expiring that will trigger independently) will have a user context for a system user. In this case this user is "System Internal Context"
lee mcdermott Posted April 7, 2022 Author Posted April 7, 2022 @Victor i still dont understand whats happened and why the call has been closed though? it just seems to have randomly closed itself with this message?
Victor Posted April 7, 2022 Posted April 7, 2022 @lee mcdermott automatic closure configured in your workflow(s) for example...
lee mcdermott Posted April 7, 2022 Author Posted April 7, 2022 @Victor no there is no auto closure, its a change request that was logged and hadnt even been actioned yet. the only closure is a node to wait for Resolution? there wasa n update on the call and the next day the next entry was this context message and the call closed? very weird?
Victor Posted April 7, 2022 Posted April 7, 2022 @lee mcdermott you can raise a support request and we can have a look at what happened on that request
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now