Hi Mingli,
Thank you for the request.
To extend the REST service is possible but I do have a couple of questions.
In all the new calls you have stated {id}
and
{pwd}
how will these be linked to uniFLOW identities?
REST Call: CheckUser- No issues just need to know which uniFLOW identities its should checkREST Call: RegisterUser – From what I can tell this call is to be used to update or assign the openId to an existing user again just need to know what identity type will hold this valueREST Call: BindWeChatUser – Not sure the purpose of this call please could you explain what should happen
In the PCL you talk about creating user in uniFLOW but I don’t see a call that would request this or should the creation of the account be tied to one of the other calls?

When creating an account should this be static or should it link to AD or other user data management source?If static what additional information / configuration should be applied to new accounts ie Groups / CC / Budgets / email etc….Should this information come from the 3rd party app or configured via uniFLOW?