Skip to main content
Contact a Moderator

Question

7
Replies
196
Views
 Binod Garg (BinodG81)
Infosys

Infosys
AU
BinodG81 Member since 2014 36 posts
Infosys
Posted: July 27, 2017
Last activity: August 3, 2017
Posted: 27 Jul 2017 1:35 EDT
Last activity: 3 Aug 2017 4:40 EDT
Closed

Issue with declare expression

We are using a declare expression on a property. However we could observe that the error message dissappears when we click on the field. This happens only for properties which are used in a declare expression . The Pega version is 7.1.9

User Experience
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 27 Jul 2017 2:04 EDT
Yaswanth Reddy Avula (YaswanthR)
Coforge DPA Private Ltd
Yaswanth Reddy Avula
Coforge DPA Private Ltd
IN

Hi Binod,


Can you attach the screenshot of the error you are facing so that we can resolve that.


Thanks,


YaswanthR
Posted: 4 years ago
Posted: 3 Aug 2017 4:31 EDT
Kautuk Shet (KAUTUKSHET)
Company Name (optional)
Consultant - CRM
Company Name (optional)
GB

Hi Binod, I was requesting you for a screenshot of the rule, not the error.  The reason was to understand if the property used in the declare expression is a source or a destination property. If you can clarify that pls.
Posted: 4 years ago
Posted: 3 Aug 2017 4:40 EDT
Binod Garg (BinodG81)
Infosys

Infosys
AU

Kautuk,


This is a source . For example if there is a declare expression using pyFirstName and pyLastName . Using these properties will result in the mentioned behaviour

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice