Hi LeeYes. Simple scenario - in the role set function and menu Task to READ only. Over client you can’t do any changes.Then post API call as <update_task><task><task_id>xxxx</task_id><description> test - API call</description></task></update_task>The change is done even if the rights in the role are saying READ only.Best RegardsMonica
For documentation purpose, might be that also others will encounter the same issue: the password is saved very good secured, with changeable key. so if we use password A, on SQL level is saved as A_encrypted_version1. Using again A later, we have on SQL level A_encrypted_version2, so way to match and check the reuse_dt since we can’t see it is password A the second time. So from mobile or others, using API the system integrity is not covered. Opened a Case by IFS and awaiting reply. Support was able to reproduce.
Hi Paul We are checking this now. Coming back with the results soon. Thank you very much for your support so far Kind Regards Monica
Dear Paul Thank you for the clarification. This was also our presumption. Anyhow: an API must keep the system integrity, there should not be a different behavior as from Screen. How to link the API call with the system parameters? Any ideas or recommendations? Kind Regards Monica
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
