And the PERFORM-ACTION processes are not included in the related workflow searches
Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe D'Souza Sent: Thursday, August 27, 2015 7:11 PM To: [email protected] Subject: Re: Minor cosmetic bug within the Expression Editor while using the MINUTE() Function... ** I did a quick check on all functions and processes to see if I see similar behavior and found those. Honestly had not noticed the process ones before too. Joe ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of LJ LongWing Sent: Wednesday, August 26, 2015 12:10 PM To: [email protected]<mailto:[email protected]> Subject: Re: Minor cosmetic bug within the Expression Editor while using the MINUTE() Function... ** I don't recall which functions were in my ticket to them, but I know I never noticed the 'perform-action' ones....you may want to open a ticket outlining your issues....:) On Tue, Aug 25, 2015 at 12:09 PM, Joe D'Souza <[email protected]<mailto:[email protected]>> wrote: ** Thanks for that LJ, Just to confirm these there functions that you saw the same behavior? LEFTC() LENGTHC() LPADC() MINUTE() RIGHTC() STRSTRC() RPADC() color codes correctly despite LPADC() having been left.. All Keywords on 8.1.2 color code correctly. Some Process actions do not color code correctly: Application-Parse-Qual-Filter (The -Filter part turns black) Application-Parse-Qual-L (The -L part turns black) Application-Parse-Qual-SField (The -SField part turns black) PERFORM-ACTION-TABLE-CLEAR-ROWCHANGED (The -ROWCHANGED part turns black) About part of the process turning black cannot be a feature because it is inconsistent where there are some Application-Parse-Qual-XXXX where the entire expression is color coded. So also with the PERFORM-ACTION-TABLE-XXXXXXX actions. Its just the one listed above that has that exception. So it does appear to be an oversight from the developers of the Developer Studio. I wonder if there is a "configuration" file somewhere within the Developer Studio's installation path that we can modify ourselves to change this behavior to what is expected.?? Joe ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of LJ LongWing Sent: Tuesday, August 25, 2015 12:37 PM To: [email protected]<mailto:[email protected]> Subject: Re: Minor cosmetic bug within the Expression Editor while using the MINUTE() Function... ** Joe, I logged a defect with BMC (SW00487794) regarding this, and other functions that aren't color coded properly in Dev Studio On Tue, Aug 25, 2015 at 10:26 AM, Joe D'Souza <[email protected]<mailto:[email protected]>> wrote: ** Right upto version 8.1.2 of the Remedy Developer Studio, if we were to set a character field extracting the minute of a DATE type field, this is how the expression would look within the Expression Editor (please view in HTML or Rich Text so you see the fonts with color).. LPAD(MINUTE($Date$), 2, "00") This sometimes makes you wonder if you had a typo somewhere in the expression. The expectation would be to have it look like.. LPAD(MINUTE($Date$), 2, "00") This was a bug with previous versions of the Developer Studios Expression Editor too. I have not yet had a chance to see if this exists on version 9. I had first noticed this in version 7.6.04 of the Remedy Developer Studio. Despite the bug in how this appears within the Expression Editor, the AR System evaluates the MINUTE() function as it should, so functionally, the function is intact. I just thought I would share this with you'll in case any of you'll wonder if you'll have made a mistake in your expression while using the MINUTE() function after noticing the color coding for it is off by a few million colors J. Joe _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
