Future ‘proof’ customizations (JS/CSS)

Remark: While this will be a really short blog post, it’s important enough to get an own post.

After creating smaller and larger customization I finally realized how I could track the smaller ones. It just took a few years. :)

The larger customizations often have a global form rule or similar. If there’s an error or a change it’s easy to identify where they are used via the Usages tab.

But there’s nothing similar for smaller modifications like the Reduced item list size. There’s nothing global it’s completely individual for a given process and yet it’s the solution for this issue.

1. Create a global constant
2. Reference it in the HTML field
3. Usages tab shows all references

This will make it really easy in the future to update any customization if something changes in a new WEBCON BPS version.