Skip to main content

I would like to share few tips which can be used when there is an introduction of lobby items during the developments. 

 


Scenario
IFS Consultants could introduce new lobby items xmls during their developments. When such delivery is installed, it is noticed that there has been an import of lobbies from mws repository. Due to the lobby content in the delivery, items related to lobby data sources, elements and pages would get checked by default (unless the selection is changed manually) in the installer during the step of Database import and deploy.  

 


Reference: https://wis.ifsworld.com/f1docs/apps9/foundation1/020_installation/500_references/020_ifs_applications_installer/020_ui_reference_itd/035_ifs_home_itd/080_import_data/default.htm?nobanner=true 

 

Recommendation for handling lobby delivery installations 
During the installation, there is a possibility to select whether to deploy the database files or not. If the "Import Lobby Items" checkboxes are ticked, all Lobby items in the repository will be deployed and existing files will be replaced by the lobby contents provided by R&D. Therefore, during an installation it's good to verify if the Lobby content should be deployed or not.  

The best way of handling the modified lobby pages when there are lobby items included in the delivery is to import the modified lobby pages manually. Then you can verify the newly updated files are available. 

Please make sure to update this in EBod Notes in necessary occasions. So that delivery could be handled accordingly. 

You could refer the updated F1 documentation further clarifications. 

Reference

https://docs.ifs.com/techdocs/Foundation1/040_administration/220_user_interface/280_lobby/060_security/default.htm

*Admin Update: Replaced wis link with docs link. (April 2020) 


Furthermore, please make sure to inform customer to have a backup of lobby items 
when there is a delivery, so that personalized modifications could be able to retrieve again.   

Hi @Minoshini Fonseka,

​Thanks for the information!
I would suggest the customer store the lobby items in a different location (simply, ask them to move it from the repository to a different location). That will prevent it from getting deployed accidentally if they have custom lobbies :slight_smile: .

Hi @Minoshini Fonseka,

​Thanks for the information!
I would suggest the customer store the lobby items in a different location (simply, ask them to move it from the repository to a different location). That will prevent it from getting deployed accidentally if they have custom lobbies :slight_smile: .

Yep Banu I totally agree with you.. I also added it as my last point to have a back up :wink:
Actually it’s a life saving tip :grinning:

This is good information. Unfortunately, once again,  you have referenced URLs that are not available to the general public!

 

https://wis.ifsworld.com/f1docs/apps9/foundation1/020_installation/500_references/020_ifs_applications_installer/020_ui_reference_itd/035_ifs_home_itd/080_import_data/default.htm?nobanner=true 

 

http://wis.ifsworld.com/F1docs/Apps9/Foundation1/040_administration/220_user_interface/280_lobby/060_security/default.htm 

This is good information. Unfortunately, once again,  you have referenced URLs that are not available to the general public!

 

https://wis.ifsworld.com/f1docs/apps9/foundation1/020_installation/500_references/020_ifs_applications_installer/020_ui_reference_itd/035_ifs_home_itd/080_import_data/default.htm?nobanner=true 

 

http://wis.ifsworld.com/F1docs/Apps9/Foundation1/040_administration/220_user_interface/280_lobby/060_security/default.htm 

The links refer to the F1 documentation which you can access in your environment using https://SERVER_URL:PORT/ifsdoc/f1doc/  (or https://SERVER_URL:PORT/ifsdoc/documentation/en/ for functional documentation)

Try replacing wis.ifsworld.com with your environment URL e.g.
http://SERVER_URL:PORT/ifsdoc/f1doc/Foundation1/040_administration/220_user_interface/280_lobby/060_security/default.htm 
 

Reply


Terms & ConditionsCookie settings