RUNMYPROCESS NATIVE VARIABLES

475 views
Skip to first unread message

con...@ecotronicbr.com

unread,
Jul 22, 2013, 9:29:20 PM7/22/13
to suppor...@runmyprocess.com
PLEASE,

ANYBODY HAVE THE LIST OF THE NATIVE VARIABLES IN RUNMYPROCESS?

FOR EXAMPLE

(P_connected_user.login), (P_Connected_user.name)

PLEASE HELP ME!

BEST REGARDS!

Dimitri MELCHIOR Pro

unread,
Jul 23, 2013, 3:23:31 AM7/23/13
to RunMyProcess Support Forum
Hi,

You will find them herebelow.

Automatic output parameters

Some parameters are set automatically at process runtime; their name starts with P_ and any name starting with that prefix must be considered as reserved for future use. The following parameters exist:

${P_result}: result of the current executed task ; the value of this parameter is modified each time a new task is executed.

${P_task}: unique identifier of the current process task ${P_task.id}. The value of this parameter is modified each time a new task is executed.

${P_task_url}: unique url of manual task form to validate or cancel a given process.

${P_index}: in the case of a task including a loop, this is the current iteration index.

${P_involved}: list of users (email) who have perform an action in process instance (P_initiator.login and successive P_user.login or user who has saved "document" on a manual task)

${P_customer}: customer identifier.

${P_header}: header of request received by an API Composite call.

${P_message}: error message when a task of a process has failed

${P_request}: unique identifier of the current process request.

${P_mode}: return state of launched process : TEST or LIVE

${P_version}: return version's name of launched process

${P_status}: return execution status of last action. It has following structure : {"name":"OK","desc":"The request has succeeded","code":200}

${P_request}: unique identifier of the current process request.

${P_branch_xxx}: when a process includes a parallel path, all variables of path xxx are grouped under that variable name (where xxx is the identifier of the branch's first step).

${P_user.xxx}: login (${P_user.login}), name (${P_user.name}), id (${P_user.id}) of the user in the current organization who has lately modified process status (he has launched process or has performed a manual task). ${P_user.extended.xxx} : allows you to access metadata of the user. ${P_user.preferences.xxx} : allows you to access preferences of the user.

${P_connected_user.xxx}: login (${P_connected_user.login}), name (${P_connected_user.name}), id (${P_connected_user.id}) of the user who is currently connected to a web form (application form or manual task form). ${P_connected_user.extended.xxx} : allows you to access metadata of the user.

${P_initiator}: same structure as P_user. User in the current organization who started the process.

${P_cookie}: value of the cookie set by the provider in HTTP header.

${P_header}: structure variable which contains the different parameters of the HTTP header (ex: P_header.cookie is equivalent to P_cookie). Learn more


Best Regards.

--

Dimitri MELCHIOR

PreSales Consultant

     

Fujitsu RunMyProcess user? Please add a review on GoogleApps Marketplace

Afin de contribuer au respect de l'environnement, merci de n'imprimer ce message qu'en cas de nécessité.
Be environmentally friendly: do not print this email unless it is entirely necessary.





--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "RunMyProcess Support Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum...@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at http://groups.google.com/a/runmyprocess.com/group/supportforum/.
For more options, visit https://groups.google.com/a/runmyprocess.com/groups/opt_out.



Reply all
Reply to author
Forward
0 new messages