Hi @Saranga Amaraweera, I was just checking if it was possible to do this with some expression that I didn’t know of. Since it is not possible, I’ve gone with your suggested approach of creating a view and using it in the existing XML Business Rule and it worked as expected. Thank you for your time and help! Regards,João Moura
Thanks once again for the clarification @ruben.maas, I think this is now clear from my side. Best regards,João Moura
Hi @ruben.maas, Thank you so much for the fast response! I still have a couple of questions, if you are able to help me clarify this out. We are using FSM on-premise, so your suggestion is to set up WinSCP (or similar) to listen to a specific folder on the machine (specified by the Business Rule Process “81”), then if WinSCP detected changes, it would upload to the client’s sFTP server in the desired folder structure, is that it? This way, since we would be implementing the requirement outside FSM, the attachment extract limitation would not be an issue. Best regards,João Moura
Hi @Sven Paul and @ruben.maas@ifs.com, First of all, thank you for the clarifications. I’ve had these fields as comboboxes previously (where the description was presented and not the code_value) but, as you even mentioned, as a best practice given the number of records contained in some of these lookups, tried to change them to lookups in order to improve the user experience but couldn’t get them to show the description, only the codes. Given your suggestions, I’ll just revert them back to comboxoes for the time being. Thanks anyway! Best regards,João Moura
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.