I remember this parameter USER_DEFAULT_COORDINATOR was working fine when using it as default filter parameter for lobbies:
USER_DEFAULT_SITE is working fine.
Any idea what might be the problem or did I use the wrong parameter to fetch the default coordinator?
Default Coordinator in User per Site has been defined.
Thanks!
Page 1 / 1
Hi, Can you please provide the steps you used to get to this point? And the issue in details?
Hi @Nalaka Samarasinghe
I used this setup:
The default parameter for coordinator is NOT working, the one for user default site is working perfectly fine.
Any idea if there are any other default-parameter I might use for the coordinator?
Thank you!
Mattis
Hi,
These are called Context Substitution Variables and are defined in Solution Manager\User Interface\Context Substitution Variables.
#USER_DEFAULT_COORDINATOR# is not setup as a Context Substitution Variable and will not work as a lobby parameter.
BR
Johan
Create your own CSV!
My created CSV finds all of the sites the user has access to - After the script is executed, users would need to sign out and back into IFS again to get it to work
FUNCTION Core RETURN VARCHAR2 IS userid_ varchar2(30); -- temp_ varchar2(32000); CURSOR get_attr IS SELECT LISTAGG(contract, ';') WITHIN GROUP (ORDER BY contract) FROM USER_ALLOWED_SITE_TAB WHERE userid = userid_; BEGIN userid_ := Fnd_Session_API.Get_Fnd_User; -- OPEN get_attr; FETCH get_attr INTO temp_; CLOSE get_attr; RETURN temp_; END Core;
BEGIN RETURN Core; END Get_All_Sites;
Then in the lobby data source you can use the following regular expression to filter by all sites as found in the CSV:
Users can type in their own sites if they wanted to narrow the filter such as: SITE1;SITE2 in the site lobby parameter