Thanks Yasas!
...just to clarify, the time required is mostly around setting up internal customers and suppliers which are the same for all sites. We are looking at using a container or a custom program for this. Let me know if you have other ideas/suggestions. Thanks!
Hi durette, I’ve been thinking in terms of best practices for sensitive data without a particular type of attack in mind but it’s something we should consider. Let me know if you have any suggestions for tables that are likely to contain sensitive info. We don’t use HR so looking at everything else.Hi William. Yes we are looking in ot OAS. I’m just looking for a list of tables that might contain sensitive data. Wondering if anyone put a list like this together.
Thanks Novishan, Can you please send me that document? I don’t have access to the internal SharePoint site. Chris
Would like to be able to reply to support emails to append replies to incidents and requests instead of requiring users to log in to portal. We use ServiceNow internally this way.
Would like to enable IFS consultants to log cases with the IFS Support Portal. We can not currently register them to access our cases directly.
We are a sand mining, processing and distribution company. Most of our plants use LabWare. We are planning to upgrade to a newer version next year. Was hoping IFS might have a LIMS module but don’t see that. We use Novacura and are considering using that to integrate LabWare with IFS. FYI, I know that IFS has a partnership with Dell for their Boomi product which handles integration. Good luck! Would like to hear what you find if you don’t mind.
FYI, there are a series of tables that you will not want to clone between your PROD and non-PROD environments in order to keep your non-PRODs from connecting with third-party production systems (“Refresh Exclusion Tables”). Below is a list of the these for Cloud 21R2 that I got from IFS. We have used this through several refreshes already. Procedurally, you have to export these before you clone the DB and then import them back after the clone. Re-Quest, our DBA services provider handles all of this for our on-premise install of Cloud. They have also automated this process for our Apps 9 install and are working on this for Cloud.Refresh Exclusion Tablesbrbase_property_tab common_messages_tab config_instance_param_tab config_instance_tab connect_envelope_tab connect_print_agent_task_tab connect_queue_tab connect_reader_tab connect_sender_tab connect_server_tab connect_simple_routing_tab connect_transformer_tab custom_connector_library_tab custom_reader_param_tab custom_sender_param_tab e
One more schema!FYI, we have found that it works best to ALWAYS export IFSIAMSYS before cloning and import this back afterwards. In other words, would suggest treating the IFSIAMSYS schema as a “refresh exclusion table” and not as a “refresh exclusion table for security” (above).
We found several ways to configure the UI:Global Context – This can be configured through Page Designer. This allows configuration of the following UI elements: menus, screens, column layouts, command buttons, field layouts, and field names on screens. Lobbies – These can be configured to provide a common UI for saved searches and My Start Page. “Job Role Templates” – We created what we called job role templates (“JRT”). This approach allows configuration of the following UI elements: column layouts, saved searches, bookmarks / shortcuts, My Start Page, table view Vs. list view. The JRT process is as follows: IT creates dummy, JRT users in IFS (e.g., “Maintenance Manager JRT”, “Shipping Admin JRT”, etc.), which can correspond with security roles if desired. BPOs log in to the JRT user accounts and configure the UI settings as desired for that role. Managers specify which JRT to use when requesting new users. IT Operations exports User Profiles from Cloud JRT accounts and imports
Here are a few more tables that I would add to the Refresh Exclusion ListRefresh Exclusion Tables Additions...ifsiamsys schema - this is mentioned above, needed to retail Azure SSO/environment. routing_address_runtime_tab fnd_branding_tab - this and the next 4 tables including brading, banners, etc. We separated these by environment with separate labels at top so users can tell which one they are in. fnd_branding_property_tab fnd_branding_resource_tab fnd_branding_token_tab
I found the same thing and logged a support case for this.
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.