Hi @Miraj ,Yes, your second option is quite right. 😎 Basically when it comes to uploading the RDLC reports to the server, the standard way is to upload them one by one via the Report Admin screen.So once the RDLC being uploaded via that screen, the RDLC will upload to the relevant path located in the server though. This path has been defined under “File Path” in the Report Admin screen though.( check the screen shot been attached) But as per your requirement , You can ask someone who has the access to the relevant server to log in to it and upload required RDLC files to the correct path via pushing them all at once.Path in the server will be → C:\inetpub\wwwroot\FSMServer_NAME\ClientReports\CustomReports Best Regards,Induwari
Hi @Hasara Dinu ,Did u check whether all the existing .RDLC reports have been copied to the above folder. Since this is a version upgrade, there is a minimal probability to removing the existing .RDLC files from both folders.Can you give it a try to upload the above .RDLC file via report admin screen and check whether the issue is occurring after that aswell..... Thanks,Induwari
Hi erin,Normally for a monitor schedule to work properly, the person id in the monitor instance screen should be equal to the value of the app param called ‘INTEGRATION_MONITOR_PERSON_ID’. Basically the values should be same..And the value comes under the app param called ‘INTEGRATION_MONITOR_PERSON_ID’ is the value you should concern about..And the person id we are putting as the value of the app param called “INTEGRATION_MONITOR_PERSON_ID’ should be consists of below requirements, for the monitor schedules to perform their expected behavior though..Person should be an ACTIVE user person should consists of his license type as STUDIO license Person should be an ADMIN user Thanks,Induwari
Hi Erin,You can search for the person id of the authorized person for the monitor schedule via the app param called ‘INTEGRATION_MONITOR_PERSON_ID’ though.And the password of that particular person should be the value of the app param called ‘INTEGRATION_MONITOR_PASSWORD’ though. Thanks,Induwari
Hi @TatRajatM , Logging is enabled through the FSM Smart Client and is written by the FSM Server. Logs can be viewed and saved from the FSM Smart Client’s Studio. a. Business Rules (BR) – Tracks business rules and their operations.b. Communication (CM) – Covers information sent to and from FSM.c. Database (DB) – Shows database interaction and usage.d. Exception (EX) – Details unexpected results from the application.e. Information (IN) – Explains how the system is currently functioning.f. Tracing (TR) – Tracks processes in the system.g. User Interface(UI Designer/ UI) – Covers UI interaction with users.h. Custom Information (CI) – Can be used by customizations.i. Custom Exception (CE) – Can be used by customizations. Each category has a level between 0 – 10. For most categories, 0 means that nothing will be logged. Each level contains the logging from all of the lower levels as well.Facts to concern about when changing the server log levels Logging effects performance. Be selective
Hi @saras360 ,you can use attached doc prepared by me to gain knowledge on how to create FSM client reports.Hope this might help you BR,Induwari
Already have an account? Login
No account yet? Create an account
Enter your username or 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.
