Hi, On a shared environment, a rule was created with the name 'li

apatil over 11 years ago

Hi,

On a shared environment, a rule was created with the name 'like' matching, one of Appian's in-built functions (from the palate category 'Text Functions'). For all the dependant rules and script tasks in the process flows, the new rule is being referred.

How to overcome this issue? Even after the rule is deleted, the issue persists. Should the cache be cleared or will this require a server restart? Looking forward for the inputs, in this regard.

Can this be included as one of the take-ins for the upcoming 'Hotfixes', preventing users from creating rules with the same names as that of the Appian's in-built functions?

Thanks !
Arvind...

Discussion posts and replies are publicly visible

Parents

0 cmtam over 11 years ago

My client had the same issue to create the topeople rule (same as Appian Function), we logged the support call and the following is the solution provided by Appian's Support:

1. If you already deleted this rule create it again as follows. Otherwise proceed to step #2
---> Create a rule called "topeople" with any definition, let's say:
--> 1.1 A single input of type "User or Group". Let's call it "userOrGroup"
--> 1.2 With the following definition: =ri!userOrGroup
2. Export it in an application
3. Delete the"topeople" rule
4. Edit this rule's XML. Change its name to "topeopleRule"
5. Put it back into the ZIP
6. Import the application
7. Delete the renamed rule if not needed
8. Restart JBoss

This will fix the issue without the need of re-mapping any models.

This is what you need to be aware of:
---> 1 Models that WERE saved/saved&published after the problematic rule "topeople" was created will have to be re-mapped. The re-mapping will work after the restart of the app server.
---> 2 Models that WERE NOT updated during the existence of the problematic rule "topeople" are NOT impacted.
---> 3 Running coming from non-modified models during the existence of the problematic rule "topeople" are NOT impacted.
---> 4 Running instances started BEFORE a model was updated and impacted by the problematic rule will NOT be impacted
---> 5 Only running instances coming from modified models started after the rule was introduced are impacted.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 cmtam over 11 years ago

My client had the same issue to create the topeople rule (same as Appian Function), we logged the support call and the following is the solution provided by Appian's Support:

1. If you already deleted this rule create it again as follows. Otherwise proceed to step #2
---> Create a rule called "topeople" with any definition, let's say:
--> 1.1 A single input of type "User or Group". Let's call it "userOrGroup"
--> 1.2 With the following definition: =ri!userOrGroup
2. Export it in an application
3. Delete the"topeople" rule
4. Edit this rule's XML. Change its name to "topeopleRule"
5. Put it back into the ZIP
6. Import the application
7. Delete the renamed rule if not needed
8. Restart JBoss

This will fix the issue without the need of re-mapping any models.

This is what you need to be aware of:
---> 1 Models that WERE saved/saved&published after the problematic rule "topeople" was created will have to be re-mapped. The re-mapping will work after the restart of the app server.
---> 2 Models that WERE NOT updated during the existence of the problematic rule "topeople" are NOT impacted.
---> 3 Running coming from non-modified models during the existence of the problematic rule "topeople" are NOT impacted.
---> 4 Running instances started BEFORE a model was updated and impacted by the problematic rule will NOT be impacted
---> 5 Only running instances coming from modified models started after the rule was introduced are impacted.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data