Custom action rules and limitations
Custom actions give users a way to customize the PROCESIO platform according to their needs, however while doing this you will need to keep in mind…
Custom actions give users a way to customize the PROCESIO platform according to their needs, however while doing this you will need to keep in mind the restrictions imposed by this technology:
- Custom actions are class libraries for .NET 8 or .NET 10. PROCESIO runs custom actions on .NET 10. A package can contain builds for several .NET versions: PROCESIO uses the newest one it supports. Custom actions you built earlier for an older .NET version keep working without a rebuild.
- Custom actions can only be written using the C# language.
- Use the nuget provided by PROCESIO. Follow the steps presented in Prerequisites and Environment setup and read the Your first Custom action to help you get started.
- Other libraries that are not offered by Microsoft need to be whitelisted with us. In the following you will see the list of the ones already whitelisted.
"WhitelistPackages": [
"Ringhel.Procesio.Action.Core",
"Newtonsoft.Json",
"JetBrains.Annotations",
"SimMetrics.Net",
"CsvHelper",
"DocumentFormat",
"DocumentFormat.OpenXml",
"DocumentFormat.OpenXml.Packaging",
"DocumentFormat.OpenXml.Spreadsheet",
"Ical.Net"
],
"WhitelistNamesapaces": [
"Newtonsoft.Json",
"System.Runtime",
"System.Linq",
"System.Threading.Tasks",
"System.Collections",
"System.Private.CoreLib",
"System.Private.Uri",
"corlib",
"Ringhel.Procesio.Action.Core",
"System.Text.RegularExpression",
"System.Diagnostics.Debug",
"System.ComponentModel",
"System.Data",
"SimMetrics.Net",
"SimMetrics",
"System.Net.WebHeaderCollection",
"System.Net.Primitives",
"System.Console",
"System.Net.ServicePoint",
"System.Net.WebProxy",
"System.Net.Requests",
"CsvHelper",
"DocumentFormat",
"DocumentFormat.OpenXml",
"DocumentFormat.OpenXml.Packaging",
"DocumentFormat.OpenXml.Spreadsheet",
"Ical.Net"
]