This content has been marked as final. Show 1 reply
I think you have two options:
1 - If your intention is to create 'User' using XAI (Web Services), use CDxUserMaintenance XAI Inbound Service, similar to below:
CILTUSEP, legacy service XMLs would have inputs in attributes as opposed to elements. You can use XAI Dynamic Submission to build above or other required XML.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <CDxUserMaintenance dateTimeTagFormat="CdxDateTime" transactionType ="ADD" > <CDxUserMaintenanceService> <CDxUserMaintenanceHeader User="RXSUSER" /><CDxUserMaintenanceDetails User="RXSUSER" LoginId="RXSUSER" UserEnable="ENBL" LanguageCode="ENG" FirstName="RXS" LastName="User" DisplayProfileCode="NORTHAM" ToDoEntries="10" TD_ENTRY_AGE_DAYS2="20" > </CDxUserMaintenanceDetails> </CDxUserMaintenanceService> </CDxUserMaintenance> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
2 - Haven't tried it but since 'USER" MO allows +BO Maintenance+, you could create a Service Script and use/duplicate BO - 'F1-IDMUser', why? because it contains the schema definition of CILTUSEP service. SS can further be exposed as a XAI Service.
Portals - you can't; Business Service - you can't.