Idea: I'd like to suggest the customization / expansion of the code-linting (aka Design Controls in design studio) capabilities that design studio currently has by allowing users to create and add their own rules. An organization should be able to customize design controls that fit their own organization's best practices (eg. verify that spied elements follow a specific naming convention) and code styles (eg. all START stages have to be font color = green) background: Most modern IDEs (eg. vscode or vs) have the capabilities to allow developers to create custom code-linting rules that fit their organization's best practice and coding styles. These rules help standardize code within an organization which can lead to improved code maintainability, improved performance, and minimize bottlenecks development (eg. code reviews). other information:
Currently, it is possible to export Design Control settings to an XML file and share it with anyone. So, it should make it possible for organizations to share their best practices with anyone, allowing new developers to benefit from the knowledge of more experienced developers. Essentially, making it possible for new organizations adopting Blue Prism to copy design controls from experienced organizations who have been using Blue Prism for years.
... View more