Used to add a new Task or to update an existing one.

bportalTaskUpdate(p_companyID, p_code, p_levelId, p_name, p_startDate, p_endDate, p_estimatedHours)

You can use this endpoint to create a new Task or update an existing Task into/from our software.

Parameters

Name	Type	Required	Description
p_companyID	string	Yes	The security code you have been provided with, string (32)
p_code	string	Yes	We will look to update the existing Task identified by the value provided, if no such Task will be found we will insert a new Task with the given code
p_levelId	string	No	Mandatory only in case we want to add a Task, during update it will not be taken in consideration.
p_name	string	No	Mandatory in case we want to add a Task, optional in case of update (leave empty for no change to it).
p_startDate	string	No	Mandatory in case we want to add a Task, optional in case of update (leave empty for no change to it).
p_endDate	string	No	Mandatory in case we want to add a Task, optional in case of update (leave empty for no change to it).
p_estimatedHours	string	No	Optional for both add/update.

Return values

INSERTED – the adding of a new Task was a success.

UPDATED – the update of the existing task was a success.

ERROR_NO_SECURITY_HASH - user did not supply p_companyId security code.

ERROR_UNKNOWN_SECURITY_HASH - supplied security code p_companyId is invalid.

MISSING_CODE – p_code parameter is missing.

MISSING_LEVEL – the p_levelId parameter is missing during add Task (during update it is ignored).

INCORRECT_LEVEL – the p_levelId parameter can have only one of the values 1, 2 or 3.

MISSING_NAME – the p_name parameter is missing during add Task.

MISSING_START_DATE - the p_startDate parameter is missing during add Task.

INCORRECT_START_DATE – the p_startDate value must be in the format yyyy-mm-dd.

MISSING_END_DATE - the p_endDate parameter is missing during add Task.

INCORRECT_END_DATE – the p_endDate value must be in the format yyyy-mm-dd.

INCORRECT_ESTIMATED_HOURS – if something provided for the p_estimatedHours value, it must be an integer number.

ERROR_SAVING_TASKTREE_FOR_PROJECT – there was a problem adding a new Project.

ERROR_SAVING – there was an unknown problem saving the Task.

Sample

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:uen="uen:esws">

<soapenv:Header/>

<soapenv:Body>

<uen:Esws.bportalTaskUpdate soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<p_companyID xsi:type="xsd:string">^4p;tU0Q+#dEIhTWkuj5FnLD^aOLqVu0</p_companyID>

<p_code xsi:type="xsd:string">2222</p_code>

<p_levelId xsi:type="xsd:string">1</p_levelId>

<p_name xsi:type="xsd:string">Task</p_name>

<p_startDate xsi:type="xsd:string">2021-01-01</p_startDate>

<p_endDate xsi:type="xsd:string">2022-01-01</p_endDate>

<p_estimatedHours xsi:type="xsd:string">100</p_estimatedHours>

</uen:Esws.bportalTaskUpdate>

</soapenv:Body>

</soapenv:Envelope>

Response

<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="uen:esws">

<SOAP-ENV:Body>

<ns1:Esws.bportalTaskUpdateResponse xmlns:ns1="uen:esws">

<return xsi:type="xsd:string">INSERTED</return>

</return>

</ns1:Esws.bportalTaskUpdateResponse>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>