Skip to main content
Version: 2.2.3

newAction

This method enables recording actions associated with an action plan. To use it, it is necessary to follow the standard documented below:

Java class
Requestweb/wwwroot/ws/java/timecontrol/NewActionRequestType.java
Returnweb/wwwroot/ws/java/timecontrol/NewActionResponseType.java

Request:

ID #RequiredDescription
ActionPlanIDXID # of the action plan to which the action belongs.
ActionIDAction ID #.
ActionTitleXAction title (What?).
CatIDX¹Action category ID #.
FgTypeActionXAction execution type.
1 - Immediate;
2 - Planned.
Note: The Immediate configuration will only be enabled if it is configured in the action plan category.
TeamIDAction team ID #.
RespIDXUser ID of the Responsible for execution (Who?).
DtPlanStartXPlanned start date (When?) in the YYYY-MM-DD format.
TmPlanStartPlanned start time (When?) in the HH:MM format. If it is not filled out, the system will consider the current time.
DtPlanEndXPlanned end date (When?) in the YYYY-MM-DD format.
TmPlanEndPlanned end time (When?) in the HH:MM format. If it is not filled out, the system will consider the current time.
VlPlanCostPlanned cost (How much?), in the 10000.00 format, where the "." is the decimal separator. Thousandth separator is not used.
DsWhyWhy?
DsWhereWhere?
DsHowHow?
DsResultX²Result.
info
  • ¹ - It will be required only if a list of allowed categories is configured in the action plan category.
  • ² - It will be required only for an immediate action to be added, and if the result is set as required in the plan category.

Request structure:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:timecontrol">
<soapenv:Header/>
<soapenv:Body>
<urn:newAction>
<!--You may enter the following 16 items in any order-->
<urn:ActionplanID>?</urn:ActionplanID>
<urn:ActionID>?</urn:ActionID>
<urn:ActionTitle>?</urn:ActionTitle>
<urn:CatID>?</urn:CatID>
<urn:FgTypeAction>?</urn:FgTypeAction>
<urn:TeamID>?</urn:TeamID>
<urn:RespID>?</urn:RespID>
<urn:DtPlanStart>?</urn:DtPlanStart>
<urn:TmPlanStart>?</urn:TmPlanStart>
<urn:DtPlanEnd>?</urn:DtPlanEnd>
<urn:TmPlanEnd>?</urn:TmPlanEnd>
<urn:VlPlanCost>?</urn:VlPlanCost>
<urn:DsWhy>?</urn:DsWhy>
<urn:DsWhere>?</urn:DsWhere>
<urn:DsHow>?</urn:DsHow>
<urn:DsResult>?</urn:DsResult>
</urn:newAction>
</soapenv:Body>
</soapenv:Envelope>

Return:

ID #Description
RecordIDSUCCESS: Action ID # recorded.
StatusReturns the status of the execution. SUCCESS on success and FAILURE on failure.
CodeReturns the execution code:
â–ª 1 - Method executed successfully;
â–ª -1 - Error in the configuration of the input parameters;
â–ª -2 - ID # of the plan or action is duplicated in the database;
â–ª -3 - The authentication user does not have the necessary permission to execute this method. Check if the user has access to the PL025 menu.
â–ª -12 - The entered ID # already exists. Please edit it;
â–ª -13 - Action plan not found;
â–ª -14 - Inexistent user;
â–ª -15 - Inactive user;
â–ª -16 - Inexistent team;
â–ª -17 - Inactive team;
â–ª -18 - Category not found;
â–ª -19 - Inactive category;
â–ª -20 - End date earlier than start date;
â–ª -21 - Plan already finished;
â–ª -22 - The user does not have permission in the entered category;
â–ª -23 - The user does not have permission in the entered plan;
â–ª -24 - The category configuration does not allow adding an immediate action;
â–ª -25 - The entered category is not in the restricted category list;
â–ª -26 - It is not allowed to use retroactive dates;
â–ª -27 - Unknown error when processing the request;
â–ª -29 - The action plan had the maximum value of the How much? field exceeded;
â–ª -30 - The action plan has already been finished;
â–ª -32 - The action plan cannot be edited because of its status;
DetailSUCCESS: Method executed successfully
FAILURE: Description of the error that was found.

Return structure:

<newActionResponse>
<RecordID>?</RecordID>
<Status>?</Status>
<Code>?</Code>
<Detail>?</Detail>
</newActionResponse>