I came accross a behaviour where an appian object(integration) accessed by two different users having parameters data type in two different format
Eg: user1 gets the data type format as "mm/dd/yyyy" and user2 gets the data type as "dd/mm/yyyy". Though their internationalisation settings are same and both users are accessing same object . What else could be the scenario for such behaviour?
Above are images from two different users using the same objects.
Discussion posts and replies are publicly visible
The settings are the same in admin console or in user config? I know that is a silly question... but just to confirm...
Maybe it's related with the browser config?
This is just how these values are displayed. It will not have any effect on the evaluation of these integrations.
when both the users are trying to run the integration with currentdate parameter as today() it is executing success for user1 with format "mm/dd/yyyy" and for the user2 it gives error "500- server error" now when i change the today value to null in current date for user2 it is success for user2
Checked the security aspect as well so the analysis came down to this as of now
How do you configure the HTTP body? Can you share that code snippet?
Its a get method where a ruleinput (currentDate) of data type 'date' is passed in the query parameters .Its calling a webAPI which is an expression rule in another appian environment. Sorry could not add the snippet.
the settings are simillar for both users
So, when you do some sort of tostring() on a date, it will be evaluated in the context of the user, including the locale. If you pass that date to the API, you might want to use the text() function to guarantee a uniform format.
let me give it a try thanks for the help !