Hi Nethli,

is this request for FSM or PSO?

Best regards
Roman

Hi Roman,

Yes, this regarding FSM. I have to work on a FSM project. 

Best Regards,

Nethli

Frist, ensure that the target and source database is on the same FSM version. Then, you can basically follow the same guidline that our Cloud Team is using when performing environment clones:

 

IFS FSM CLONING PROCESS UPDATE

The service of updating data in one client environment with data from another client environment is known as environment cloning. The actual name of this service is "Environment Cloning," although it is also frequently called "environment refresh", "environment copy", "database clone", "database refresh", and "database copy." In a cloning activity, "Data" refers to the information kept in the database, which includes system parameters and metadata in addition to business data. In all scenarios, the target environment will get the source environment's data except for environment-specific basic data, integrations, connect configurations, App parameters, etc which are retained in the target environment. This is achieved by exporting tables such as metrix_app_params, threesixty_app_params, cust_image tables, cust_app_params, intergration_monitor, cust_int_routing_rule and cust_int_routing_argument from the target environment before cloning and re-importing them into the environment after cloning.

 

IFS CSC team does not copy attachments from the source environment Azure storage account ( Such as images, files, etc.) to the target environment. Testing should therefore only be done on requests, tasks, etc. with attachment records made in the target environment.

 

Effective from the 1st of July 2023, we will be introducing a significant upgrade to our service by incorporating the ability to copy "Custom Reports" from the source environment to the target environment, based on the customers' feedback.

 

Customers will be given the option to select whether they require Custom Reports to be copied or not from the source environment to the target environment when raising the FSM cloning request.

 

While we are thrilled to offer this new functionality, we kindly request our customers to be aware of an important aspect of the process. Upon performing the clone, the custom reports of the target environment will be overwritten. Therefore, we advise the customers to take the necessary precautions and ensure the preservation of any work that has not been migrated to the source environment.

The attachments in on-premise environment are by default stored in the “M5Attachments” folder within the FSM App Server IIS root directory. Custom Reports can be found in the FSM Server root directory as well. 

After the backup file has been imported into the DB Server, you will have to re-run the FSM Installer “Application Server & Clients” part to reconfigure the database connection (e.g. changing database user name, etc.)

Best regards
Roman

Thanks Roman!!