Jump to content

Recommended Posts

Posted

This morning we are getting reports of needing to enter reasons for changing sub-statuses where yesterday there was no reason information needed.

Something has happened since the last update last night...can this ne looked into please?

Posted

@Jeremy from the release notes for the latest Service Manager update:

  • On Hold Request reason not always mandatory when status set to mandatory {PM00176494}

 

Can I ask if your sub status is configured as mandatory or not?

Alex

Posted

It would seem today ours have switched to Mandatory bar two "Assigned Service/Incident" and changing "Reason required" wont allow me to save the change (while published?). I'm reluctant to switch to Draft while it's actively in use. 

Posted

Also I went through yesterday and changed our global statuses to be non-mandatory and this morning they are mandatory again!

Posted

Why do you have to enter a Alternative Name...surely that should be optional?

We don't expose this information to the customer so it's a little redundant for us. I have updated this will a full stop which has enabled us to save the status, thanks for the clarification.

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...