Agent Handling

This function returns the record used during activity number activity_no and step number step_no and process id the process_id. Usually, there are as default values the current activity, current step, and current process.



This function creates a running agent using the prototype agent aname and returns the handle of the agent.



This procedure starts the action plan of the agent with handle ahandle. The parameters p1,...,p10 are optional and can be omitted. The agent first must be created by agent_create. It can be called both “call“ and “callwait“



This procedure frees the agent with handle ahandle.



We call this procedure inside the action code of an agent. The varname becomes public for all other agents. If another agent calls the agent_getvar function, it can get the value(s) of varname.



This function returns the variable varname with offset varoff of the agent ahandle. A call must previously set the variable to agent_setvar into the corresponding agent‘s action code.



We use the DisableAllFields when the fields of a form are too many, and it is better to disable all fields and then enable only a few fields we want. Keep in mind that in this case, the contents of the fields are visible to the user.



We use the HideAllFields when the fields of a form are too many, and it is better to hide all fields and then show only a few fields we want.



If we have used the DisableAllFields then the EnableField enables the fieldname field of the form.











If we have used the HideAllFields then the ShowField becomes visible in the fieldname field of the form.



The RequiredField specifies a field fieldname as a required one. The form does not save to the database until the field we have filled in with data. The prompting label of the field becomes bold to notify the required of the field.



The SetValue presets the value of a form field fieldname to the value val. If the fieldname represents a lookup field (foreign key), then the displayval is also required. (the val, in this case, is kept internally while the displayval is displayed)









This procedure creates an agent according to the prototype aname and activates the new agent. The parameters p1,..p10 are optional and can be omitted. The variation _debug is for debug purposes from the side of the programmer. The variations “coordinator“, “expert“, “planner“, “agent“ are given for clarification into the code context.



This procedure assigns the activity step_descr to user uname or role rname. If the assignment occurs at a later time, the date0 is this time as a number. The parameters can pass to the user as p1,..,p10, and we can omit them. This, can we call it as “call“ or “callwait“. Also, we call this procedure inside the action code of a coordinator.



This function assigns a piece of information named info_descr to user uname or role rname. The parameters can pass to the user as p1,..,p10, and we can omit them. The returned value id is the unique field value of the AU_STEP record.



This procedure waits for the event event_descr to happen. There is no user interaction at all. The system checks only the validation code section of this event to see if a value of result (1) returns to continue executing the coordinator workflow. Can we pass the parameters as p1,..,p10, and we can omit them. Also, we can call it “callwait.“ Finally, we call this procedure inside the action code of a coordinator.



This procedure sets the comment of a coordinator agent to comm. We can call it inside the agent‘s action code.



This procedure sets the comment of a coordinator agent to comm, especially for the activity to follow. We can call it inside the agent‘s action code.



This procedure sets the coordinator‘‘ owner user as uname. Thus, the procedure owner can see from his terminal all of the paths of the coordinating procedure.



This procedure opens a form for the agent with handle ahandle and only shows the agent‘s status for administrative purposes.



This procedure sets the time limit of the activity (defined in days)



This procedure sets the final date of the activity (as a date string)



This procedure sets the monitoring of the activity (True or False)



This procedure sets the staying property of the activity (True or False)



This procedure sets the day to offset from the starting of the procedure (as a number)



This procedure sets the parent activity of the activity.



This procedure sets the priority of an activity (smaller number is (1))



This procedure sets the comments of the activity.



This procedure sets the resource group of the activity.



This procedure sets the id record of the activity that is going to be issued.



This procedure sets the “Activity“ field of the activity.



This procedure sets the business id of the activity.



This procedure sets the product id of the activity.



This procedure sets the contact id of the activity.



This procedure sets relations between activities and other entities. For example: