Can you not do the if comparison in the request form offering in a hidden field? You can call the users current details using the $(CurrentUserField("FirstName")) etc. and compare that to your captured values.
With the formula
if ToUpperCase(NewFName) == ToUpperCase(StoredFName)
I used ToUpperCase() so that the case doesnt cause a mismatch but if you want the case to be checked as well just remove the function.
Thanks for replying!
This is actually my Plan B, to do the comparison form side and set checkbox's.
While this method works, it becomes problematic for me because I have another form that has multiple check boxes on both the "Current Stored Value" side and "New Value" side. Thus I would have to create a checkbox for every comparison, which I didn't want to do.
Ironically in the one of the Update Blocks of the workflow I'm able to use Expression Logic to determine the delta changes and write those in the Description field of the Service Request, with the intention of making it clear what exactly the customer is requesting to change. Example:
I've put in a feature request to expand the capabilities of the IF Block, according to support others have also requested this.
In the old HEAT classic version I was able to do this quite easily:
I agree the old HEAT Classic IF block actually worked quite well (and still does!!!). The Prompt and Execute function in ISM (201x.x) has also been depreciated now so we could do with an enhanced IF block. Can you let me know the RM# so I can track it?
I opened it yesterday but haven't received the RM yet (probably hasn't been seen yet by development). One of the support agents did however mention there were a few previous RM's opened (by other customers) but were all cancelled or sitting idle with no movement. I'm hoping these features get more traction.
Will post back once i get it.
Ran into a similar issue - had to test if the Submitter was an approver on a Service Request. Tried this and it worked like a charm.