editAction
This method enables editing an action from an action plan. To use it, it is necessary to follow the standard documented below:
Java class | |
---|---|
Request | web/wwwroot/ws/java/timecontrol/EditActionRequestType.java |
Return | web/wwwroot/ws/java/timecontrol/EditActionResponseType.java |
Request:
ID # | Required | Description |
---|---|---|
ActionPlanID | X | ID # of the action plan to which the action belongs. |
ActionID | X | Action ID #. |
ActionIdNew | New action ID #. | |
ActionTitle | X | Action title (What?). |
CatID | Action category ID #. | |
TeamID | Action team ID #. | |
RespID | X | User ID of the Responsible for execution (Who?). |
DtPlanStart | Planned start date (When?) in the YYYY-MM-DD format. | |
TmPlanStart | Planned start time (When?) in the HH:MM format. | |
DtPlanEnd | Planned end date (When?) in the YYYY-MM-DD format. | |
TmPlanEnd | Planned end time (When?) in the HH:MM format. | |
VlPlanCost | Planned cost (How much?), in the 10000.00 format, where the "." is the decimal separator. Thousandth separator is not used. | |
DsWhy | Why? | |
DsWhere | Where? | |
DsHow | How? | |
DsResult | Result. |
Request structure:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:timecontrol">
<soapenv:Header/>
<soapenv:Body>
<urn:editAction>
<!--You may enter the following 16 items in any order-->
<urn:ActionPlanID>?</urn:ActionPlanID>
<urn:ActionID>?</urn:ActionID>
<urn:ActionIdNew>?</urn:ActionIdNew>
<urn:ActionTitle>?</urn:ActionTitle>
<urn:CatID>?</urn:CatID>
<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:editAction>
</soapenv:Body>
</soapenv:Envelope>
Return:
ID # | Description |
---|---|
Status | Returns the status of the execution. SUCCESS on success and FAILURE on failure. |
Code | Returns 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. â–ª -11 - Action plan not found; â–ª -12 - Action not found; â–ª -13 - The user does not have permission in the plan; â–ª -14 - The user does not have permission in the category; â–ª -15 - The action ID # cannot be edited; â–ª -16 - The action cannot be edited because of its status; â–ª -17 - The entered ID # already exists. Please edit it; â–ª -18 - Inexistent user; â–ª -19 - Inactive user; â–ª -20 - Inexistent team; â–ª -21 - Inactive team; â–ª -22 - Inexistent category; â–ª -23 - Inactive category; â–ª -24 - The end date cannot be before the start date; â–ª -25 - Plan or action already finished; â–ª -26 - The user does not have permission in the entered category; â–ª -27 - The category selected for the action is not among those allowed in the action plan category; â–ª -28 - Retroactive dates are not allowed; â–ª -29 - The validation flow has been successfully executed, but there was an unknown error while processing; -30 - The action plan had the maximum value of the How much? field exceeded; â–ª -31 - Cancelled action; â–ª -32 - The action plan cannot be edited because of its status. |
Detail | SUCCESS: Method executed successfully FAILURE: Description of the error that was found. |
Return structure:
<editActionResponse>
<Status>?</Status>
<Code>?</Code>
<Detail>?</Detail>
</editActionResponse>