Multiple Rules in Process

vinsnash

I really need some help with this because I'm dead in the water with this one. I have to create an instance for a transaction history object when I've added a new member to the member object. I've tried every way I can think of.

In a process to enter a new member I cannot get another action to execute after "Enter New .... Using Main"

Examples:

Enter New NSCPers Using Main

DISPLAY MESSAGE 'New Member Added'

I've tried using a 2nd named rule. I've tried naming another process. All with no success.

The closest I've got was to add a rule to the object.

IF NSCPers IS NEW THEN

CREATE Pending WITH ...etc.

Even though I specifically check "Do not use during initialization" I can see in the log file that the 'CREATE' executes as soon as the main form of the object is displayed. I select the process from the menu, the main form displays, then I check the log file and there it is. The CREATE executes again later in the procedure. I end up with two identical instances of "Pending".

ACDC

So whats wrong with adding a rule to the Object, It seems to be the only way of handling a background transaction, especially for audit and accounting purposes

vinsnash

I tried adding a rule to the object

IF NSCPers IS NEW THEN

CREATE Pending With .....etc

In the advanced rule edit tab I select 'do not use in initialization'. Even so, when the NSCPers main form is displayed the CREATE action executes before any values are added to attributes of NSCPers and then again later in the procedure. Both executions are viewable in the log. I end up with two identical instances of Pending.

I'm using 4.9 build 1301. Support has tried it using 5.0 and doesn't have a problem. I find it hard to believe this hasn't been done before successfully by somebody prior to 5.0.

tford

I've done it before, but have no idea what build I was on at that point.

ACDC

maybe i don't fully understand what you are trying to do.

but if you are trying to create an Audit/History trail when a new user is created or changed then I would create an Audit object and link it to your User object. So the User object owns the Audit object

Then place a rule in the User object that in turn links to the process of creating the Audit instance
eg:

IF User is NEW then
CreatAuditProcess (pcess

ACDC

IF User is NEW then
CreatAuditProcess (this is the process that will be activated by the rule)

vinsnash

Sorry for the late reply. I had to drop the ball for a few days. Anyway your suggestion is the way to go. I would have thought a process could execute another process, but I guess not.

tford

I would have thought a process could execute another process, but I guess not.

Yes, a process can execute another process.