Guidelines for Creating Request XML for Users Roles and Permissions

The following are the guidelines for creating request XML for users roles and permissions:

  • Transactions — Roles, users, and permissions must always be in different transaction boundaries. Two different roles, users, or permissions can be in different transactions. Either all business objects in a transaction are imported or none of them are imported.
  • Functions and HtmlElements must be synchronized by the user separately. It is not a part of copy metadata. Ideally, functions come with seed data and not created by the users. Roles get associated with a function when roles are exported. If such a function is not defined in the seed data of destination company, an exception is thrown.
  • Only one command per transaction is allowed.
  • You can have multiple transactions per request or response.
  • Only one type of input per command is allowed. That is, either of Users, Roles, or Permissions per command is allowed. Implicitly, only one type of input is allowed in one transaction.
  • Other business objects such as repository and so on cannot be exported along with users, roles, and permissions. They cannot be a part of the same request.