1 of 1 people found this helpful
This may be due to validation of the values selected in Template and the value that has to be there for a change request. The template might be having an inappropriate value selected for the user submitting the change. So when the user tries to submit with the same value an error message is raised.
An other possibility for this issue is, the user might have entered a value manually in a list box field, but the value should have been selected from a predefined list.
Note: For any QA related engagements in BMC Remedy please feel free to call us.
Thank you for the help - I'll check their template and see if that might
be the issue.
Thank you -
Check out both suggestions and could not find any issues with the way they
built the template or the selection of items not defined in the
template..... any other suggestions?
1 of 1 people found this helpful
I think this error has something to do with the default group of the user creating the change and selecting the template - I don't remember all the details, but if their default doesn't match the template's default group or something like that you get that error.
You can try, with one user, changing their default group to the - I think "authored by" - group on the template and see if that changes it. To be honest, I just disabled the filter that popped up the error on my demo system. Just got too annoyed by it. It didn't seem to cause any harm, but obviously you might want to test it out...
Look at filter CHG:CRQ:ValidateRqstGrp_151
(If your error msg has a different filter, can check whatever filter it is)
If you get an "assignment not valid" error, look at filter
check the integrity of the Requester Support Group Field.... Requester Support Group Name, Requester Support Group ID should be intact with each other..
I guess when applying Template this integrity is broken... enable the logs check the open window and close window mapping there should be something mapped on to the Requester Support Group Name or ID...if missing out map it in the Close Window if Requester Support Group info is getting transferred from the Template Selection Dialog then Requester Support Group ID should also be transferred or mapped back to the Parent...in that way we would not align the integrity of this entity (Requester Support Group)
I think during open window (on clicking Template Button) we would pass in the Requester Support Group(Default Support Group) to fetch down and show the list of Templates ....and when the users try to change the Support Group and view the Templates then after during close window we would pass in back the Requester Support Group details...
I would say if there is a mapping exists in the close window it should be there for both the fields Requester Support Group Name and ID.... or it should not be there at all for both the fields...
I have been working on 7.6.04 SP2. I am getting the same error.
I solved it once by assigning the default assignment to that particular group.
But the same problem occurred the other day.
The other problem I have been facing with change template is that I cannot use one template for more than 1000 times.
Looks like some field values set during CR form load (in new mode) are partially being overwritten while applying the template which is leading to mismatch in requestor name / groups or so.
Looks like a defect. Check with BMC support for any available hotfix.