04-30-2020 12:51 PM
I had a fun conversation with a System Admin earlier in the week. This admin came from a strict software development background. They shared with me a frustration that OnBase Solutions are not Refactorable. I don't think I have ever heard a Sys Admin use this term or heard this perspective before.
I found the conversation interesting. I feel like parts of OnBase can definitely be refactored. Maybe I am using the context incorrectly here. For example, I have "redesigned"(my vision of refactoring) workflows with different logic to do the same process with less rules and actions (especially when Set Property to Expression was introduced). Other places, I know changes are challenging if not impossible. Shoutout to all my Sys Admins with lots of ZZZ AFKS and zzzz MIKGs : )
What do you think? Have you ever "refactored" your OnBase Solution?
05-01-2020 06:09 AM
It is especially true with WorkView life cycles. Logic tends to be more extensive and even though you can technically build a new LC to keep your previous configuration, it can be a daunting task with some configurations.
05-01-2020 07:15 AM
While this isn't "git", per se, I did want to put out there that in EP2 and EP3, we introduced Change Control tools in OnBase Studio.
https://community.hyland.com/technical/change-control
Details on it can be found in the System Administrator MRG:
05-01-2020 02:20 PM
Is WorkView supported in EP2 and EP3's change control? I don't see it listed in the SysAdmin MRG for EP3.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.