Highlights

• SOA repository for .NET assembly in GAC
• NET assembly stored in physical location
• Security for SOA repository
• Reuse existing objects within processes
• Access objects without writing wrappers or custom code
• Enables just-in-time activation of objects within processes

Click to Enlarge

Business Scenario

Company X has an HR system to track employee information like leave, salary, staff promotions etc., which has been custom-developed using Microsoft.NET technology. In order to lend advanced workflow features to their existing HR system, they decide to integrate it with Skelta BPM.NET.

In the appraisal process, there is a need to get Employee information to route the workflow based on the employee’s experience level and grade. The existing HR system already has a .NET object ‘Employee,’ which returns employee-specific details. The need is to reuse the same object inside the Skelta process and avoid custom coding.

This objective can be achieved by using Skelta Object Access (SOA). Skelta provides users with a facility to register their .Net assemblies by using SOA. This way, the company can register its Employee.dll, which is part of the HR system.

Once the assembly is registered in SOA repository its methods and properties will be accessible and can be used as expressions in the Skelta Process Designer.

Click to Enlarge