Related content:

Question Getting error when used validation rule . Kindly suggest Question Getting LockRequired error on submit when case is opened for more than 30 mins and is configured use optimistic locking Question Getting error when logging into the enviornment Question Need to alert User on Inactive over a case for more than some time particular case Question Agent Stops after Getting some error Question get error message regarding to type case when use obj-browser. any suggestion? Question Run Time Error Question Getting error as "The work object references a different assignment than the current one." when opening the case from WorkList/WorkBasket Question Changing the case management error message into pop-up message Question Token field is throwing error in Jenkins task if entering more than 32 chars.
Contact a Moderator

Question

2
Replies
213
Views
santhoshram Member since 2012 13 posts
Mphasis
Posted: 4 years ago
Last activity: 4 years 3 months ago
Closed

when i use more than 512 char in the message rules its getting truncated in run time when configured into the error icon . please suggest some solution

when i use more than 512 char in the message rules its getting truncated in run time when configured into the error icon .please suggest some solution ( 6.3 SP1)

 

***Updated by moderator: Lochan to add Categories

Case Management Low-Code App Development Dev/Designer Studio
Close popover
Moderation Team has archived post
Posted: 4 years ago

Can you please share the screenshots for the behaviour?

Posted: 4 years ago

Hi


Are you talking about this error call out that appears when you put your mouse pointer over the error cross mark ? ( Find attached ).


I can see the same behavior at my end where it is restricting it to 512 characters. I am not totally sure the underlying rule that is blocking it but from user experience prospective, i think it is good to have such limitations. As you might have noticed, the call out vanished automatically after few seconds, so with the limited time , it is difficult for user to read more than 400 characters. Also, it does not look good to show such big error message in form of call outs.


A better alternative could be to display them as page level error message on top of harness. 


 
Share this page LinkedIn
Copied!