Welcome to the Tango FSE Procedures API documentation. This document contains a detailed description of each part of the API with some examples. The best way to start exploring the main capabilities of a procedure is the T:Tango.FSE.Procedures.IProcedureContext interface.

A procedure is a sequence of a pre-programmed actions/commands. A procedure can have one or more user input parameters. A procedure can have one or more output values. Procedures are not legacy “stubs”. They are a completely different creature. Procedures are a way for providing immediate and dynamic response for almost any scenario or issue that is being raised by customers/technicians. Procedure programmers can leverage an intuitive and extensive API and accomplish almost any requirement. Programming and managing Procedures is done through the “Procedure Designer” module.

The procedure designer module can be seen as a fully fledged IDE (Integrated Development Environment), designed to provide the best development experience for the “procedure programmer”. The procedure designer is basically a project editor. In the technical sense, a “Procedure” is basically a project. A project can be composed of one or more script files that are automatically linked together. A project, is represented as a single file (.pproj) and is designed to encapsulate all the files and information about the project. A project can have multiple assembly references and make use of them. An assembly reference can be any DLL file from the entire .NET framework, or from Twine’s libraries. A “Procedure” in the “Procedures Module” is actually a single published procedure project. A published procedure is a project that is saved on Twine’s global database (per environment). Each published project has a name, description and version, while preserving the history of the last 10 versions. When the user navigates to the Procedures Module, Tango FSE will retrieves all published projects from the server. Accessing the procedure designer module requires the “Run Procedure Designer” permission. Publishing a procedure project requires the “Publish Procedure Projects” permission. Summery: Published procedure projects are intended for all users and can be executed using the Procedures Module. Procedure Project files are intended for Twine’s programmers and technicians and can be executed/edited using the Procedure Designer. We can say that once a procedure project that is being designed for end-users, is well-tested and optimized, it can be published and be available as a “Procedure” for end-users.