Directrices de desarrollo

For more information related to the process of integrating with UiPath, please access the FAQ at this link.

With respect to development guidelines, please find below the standards for creating a custom activity for the UiPath platform. For reference, the current UiPath integrations are accessible here.

1. Nomenclatura

• Los paquetes de actividades deben tener uno de los siguientes formatos:
  • Company.Product.Activities (p. Ej. UiPath.Orchestrator.Activities)
  • Company.Product.Feature.Activities (p. Ej. UiPath.Orchestrator.Webhooks.Activities)
• The UiPath namespace is reserved for packages created by UiPath Inc. and may not be used by outside developers.
• Los ámbitos deben incluir el nombre de la empresa o del producto (p. Ej. Use el ámbito de Uipath en lugar del ámbito de la aplicación).
• La categoría en el panel de actividad de Studio debe ser Company Name > Product Name > Feature Name (p. Ej. UiPath> Studio> Clic).

2. Dependencias

• Must be referenced in the Dependencies section of the NuGet package. This can be easily done in Nuget Package Explorer or in the packages.config file. In order to keep package sizes to a minimum, do not include dependency DLLs within the package itself unless necessary.

  

  

• Use exact package versions (that is, 1.0.6 not >1.0.6)

3. Iconos

• The package must have an icon. This may be done via Nuget Package Explorer or directly in the .nuspec file.

  

• Cada actividad debe tener un icono.

See here for instructions on adding icons to your activities.

4. Licencia

• The package must contain a license and require acceptance of that license. Apache 2.0 is the default and can be found here. This may be done in Nuget Package Explorer or directly in the .nuspec file.

  

  

5. Descripciones

• A summary description must be added to the package, either through Nuget Package Explorer or directly in the .nuspec file.

  

  

• Each activity in the package must have a summary description. This may be added in the DesignerMetadata.cs file. See here for instructions on how to do so.

  

• Cada propiedad / argumento dentro de una actividad debe tener una descripción.

  

• Las descripciones en los campos de las clases personalizadas también son útiles, pero no son obligatorias.

6. Varios

• La versión estable de UiPath Studio en el momento del lanzamiento debe ser compatible.
• Se prefiere la internacionalización, pero no es obligatoria.