@uipath/delegate-sdk 1.203.1 → 1.203.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +41 -3
- package/dist/index.mjs +2 -2
- package/dist/skills/business-analysis/SKILL.md +729 -0
- package/dist/skills/business-analysis/as-is-capture.md +444 -0
- package/dist/skills/business-analysis/assets/progress.yaml +19 -0
- package/dist/skills/business-analysis/assets/task-list.md +34 -0
- package/dist/skills/business-analysis/automation-hub-publishing.md +47 -0
- package/dist/skills/business-analysis/bpmn-to-be-design.md +274 -0
- package/dist/skills/business-analysis/case-to-be-design.md +223 -0
- package/dist/skills/business-analysis/diagram-authoring.md +224 -0
- package/dist/skills/business-analysis/industry-gaps.md +134 -0
- package/dist/skills/business-analysis/interview-spine.md +297 -0
- package/dist/skills/business-analysis/locales/de.json +54 -0
- package/dist/skills/business-analysis/locales/en.json +54 -0
- package/dist/skills/business-analysis/locales/es-MX.json +54 -0
- package/dist/skills/business-analysis/locales/es.json +54 -0
- package/dist/skills/business-analysis/locales/fr.json +54 -0
- package/dist/skills/business-analysis/locales/ja.json +54 -0
- package/dist/skills/business-analysis/locales/ko.json +54 -0
- package/dist/skills/business-analysis/locales/pt-BR.json +54 -0
- package/dist/skills/business-analysis/locales/pt.json +54 -0
- package/dist/skills/business-analysis/locales/ro.json +54 -0
- package/dist/skills/business-analysis/locales/tr.json +54 -0
- package/dist/skills/business-analysis/locales/zh-CN.json +54 -0
- package/dist/skills/business-analysis/locales/zh-TW.json +54 -0
- package/dist/skills/business-analysis/pdd-generation.md +204 -0
- package/dist/skills/business-analysis/pdd-template.md +562 -0
- package/dist/skills/business-analysis/progress-presentation.json +13 -0
- package/dist/skills/business-analysis/recording-first.md +19 -0
- package/dist/skills/business-analysis/recording-processing.md +152 -0
- package/dist/skills/business-analysis/references/automation-hub-open-api.md +57 -0
- package/dist/skills/business-analysis/references/case-definition-spec.md +90 -0
- package/dist/skills/business-analysis/references/case-design-patterns/loan-origination-spec.md +86 -0
- package/dist/skills/business-analysis/references/component-type-mapping.md +52 -0
- package/dist/skills/business-analysis/references/uipath-products/case-management-schema.md +62 -0
- package/dist/skills/business-analysis/references/uipath-products/maestro-case-framework.md +65 -0
- package/dist/skills/business-analysis/references/uipath-products/maestro-case-management.md +49 -0
- package/dist/skills/business-analysis/research-offer.md +104 -0
- package/dist/skills/business-analysis/research-pass.md +149 -0
- package/dist/skills/business-analysis/scripts/assemble-pdd.ps1 +294 -0
- package/dist/skills/business-analysis/scripts/assemble-pdd.sh +453 -0
- package/dist/skills/business-analysis/scripts/check-phase-ready.ps1 +72 -0
- package/dist/skills/business-analysis/scripts/check-phase-ready.sh +98 -0
- package/dist/skills/business-analysis/scripts/lint-diagram.ps1 +524 -0
- package/dist/skills/business-analysis/scripts/lint-diagram.sh +519 -0
- package/dist/skills/business-analysis/scripts/stamp-pages.ps1 +363 -0
- package/dist/skills/business-analysis/scripts/stamp-pages.sh +360 -0
- package/dist/skills/business-analysis/to-be-design.md +199 -0
- package/dist/skills/confluence/SKILL.md +386 -0
- package/dist/skills/doc-coauthoring/SKILL.md +295 -0
- package/dist/skills/excel-architect/SKILL.macos.md +161 -0
- package/dist/skills/excel-architect/SKILL.md +180 -0
- package/dist/skills/excel-architect/SKILL.windows.md +61 -0
- package/dist/skills/excel-architect/archetypes/01-financial-model-advanced.md +332 -0
- package/dist/skills/excel-architect/archetypes/01-financial-model.md +248 -0
- package/dist/skills/excel-architect/archetypes/02-data-analysis.md +171 -0
- package/dist/skills/excel-architect/archetypes/03-tracking-dashboard.md +160 -0
- package/dist/skills/excel-architect/archetypes/04-project-planning.md +193 -0
- package/dist/skills/excel-architect/archetypes/05-simple-table.md +111 -0
- package/dist/skills/excel-architect/building.md +279 -0
- package/dist/skills/excel-architect/create.md +64 -0
- package/dist/skills/excel-architect/data-and-formulas.md +186 -0
- package/dist/skills/excel-architect/generator.md +272 -0
- package/dist/skills/excel-architect/macos/scripts/add-data-validation.applescript +242 -0
- package/dist/skills/excel-architect/macos/scripts/append-rows.applescript +310 -0
- package/dist/skills/excel-architect/macos/scripts/apply-conditional-format.applescript +565 -0
- package/dist/skills/excel-architect/macos/scripts/autofit-columns.applescript +79 -0
- package/dist/skills/excel-architect/macos/scripts/benchmark.sh +135 -0
- package/dist/skills/excel-architect/macos/scripts/check-compile.sh +30 -0
- package/dist/skills/excel-architect/macos/scripts/clear-range.applescript +152 -0
- package/dist/skills/excel-architect/macos/scripts/copy-paste.applescript +179 -0
- package/dist/skills/excel-architect/macos/scripts/create-chart.applescript +531 -0
- package/dist/skills/excel-architect/macos/scripts/create-pivot.applescript +443 -0
- package/dist/skills/excel-architect/macos/scripts/create-sheets.applescript +264 -0
- package/dist/skills/excel-architect/macos/scripts/create-workbook.applescript +92 -0
- package/dist/skills/excel-architect/macos/scripts/delete-chart.applescript +105 -0
- package/dist/skills/excel-architect/macos/scripts/delete-sheet.applescript +127 -0
- package/dist/skills/excel-architect/macos/scripts/filter-data.applescript +213 -0
- package/dist/skills/excel-architect/macos/scripts/find-replace.applescript +238 -0
- package/dist/skills/excel-architect/macos/scripts/format-range.applescript +531 -0
- package/dist/skills/excel-architect/macos/scripts/freeze-panes.applescript +133 -0
- package/dist/skills/excel-architect/macos/scripts/get-current-file.applescript +24 -0
- package/dist/skills/excel-architect/macos/scripts/get-sheet-dimensions.applescript +115 -0
- package/dist/skills/excel-architect/macos/scripts/health-check.applescript +704 -0
- package/dist/skills/excel-architect/macos/scripts/list-open-workbooks.applescript +80 -0
- package/dist/skills/excel-architect/macos/scripts/maximize-window.applescript +47 -0
- package/dist/skills/excel-architect/macos/scripts/merge-cells.applescript +227 -0
- package/dist/skills/excel-architect/macos/scripts/open-workbook.applescript +139 -0
- package/dist/skills/excel-architect/macos/scripts/read-range.applescript +267 -0
- package/dist/skills/excel-architect/macos/scripts/rename-sheet.applescript +231 -0
- package/dist/skills/excel-architect/macos/scripts/select-sheet.applescript +133 -0
- package/dist/skills/excel-architect/macos/scripts/set-tab-color.applescript +109 -0
- package/dist/skills/excel-architect/macos/scripts/sort-data.applescript +136 -0
- package/dist/skills/excel-architect/macos/scripts/undo.applescript +59 -0
- package/dist/skills/excel-architect/macos/scripts/workbook-lifecycle.applescript +149 -0
- package/dist/skills/excel-architect/macos/scripts/write-formula.applescript +225 -0
- package/dist/skills/excel-architect/macos/scripts/write-range.applescript +351 -0
- package/dist/skills/excel-architect/reference/api/advanced.md +381 -0
- package/dist/skills/excel-architect/reference/api/basic.md +747 -0
- package/dist/skills/excel-architect/reference/guides.md +348 -0
- package/dist/skills/excel-architect/reference/repair.md +174 -0
- package/dist/skills/excel-architect/reference/troubleshooting.md +46 -0
- package/dist/skills/excel-architect/scripting.md +266 -0
- package/dist/skills/excel-architect/styling-and-features.md +433 -0
- package/dist/skills/excel-architect/windows/api/composites.md +337 -0
- package/dist/skills/excel-architect/windows/api/scripting.md +139 -0
- package/dist/skills/excel-architect/windows/examples/level-1-workflows.md +485 -0
- package/dist/skills/excel-architect/windows/examples/level-2-advanced.md +690 -0
- package/dist/skills/excel-architect/windows/examples/level-3-scripting.md +337 -0
- package/dist/skills/github/SKILL.md +446 -0
- package/dist/skills/github/recipes/add-comment.md +85 -0
- package/dist/skills/github/recipes/check-pr-status.md +122 -0
- package/dist/skills/github/recipes/compare-branches.md +79 -0
- package/dist/skills/github/recipes/create-issue.md +103 -0
- package/dist/skills/github/recipes/create-pr.md +97 -0
- package/dist/skills/github/recipes/get-file-contents.md +76 -0
- package/dist/skills/github/recipes/get-last-commit.md +128 -0
- package/dist/skills/github/recipes/list-my-open-prs.md +105 -0
- package/dist/skills/github/recipes/list-recent-commits.md +84 -0
- package/dist/skills/github/recipes/search-issues.md +115 -0
- package/dist/skills/google-workspace/SKILL.md +217 -0
- package/dist/skills/google-workspace/services/calendar.md +311 -0
- package/dist/skills/google-workspace/services/docs.md +426 -0
- package/dist/skills/google-workspace/services/drive.md +504 -0
- package/dist/skills/google-workspace/services/gmail.md +466 -0
- package/dist/skills/google-workspace/services/sheets.md +370 -0
- package/dist/skills/internal-comms/SKILL.md +35 -0
- package/dist/skills/internal-comms/examples/3p-updates.md +47 -0
- package/dist/skills/internal-comms/examples/company-newsletter.md +65 -0
- package/dist/skills/internal-comms/examples/faq-answers.md +30 -0
- package/dist/skills/internal-comms/examples/general-comms.md +15 -0
- package/dist/skills/jira/SKILL.md +397 -0
- package/dist/skills/jira/recipes/add-comment.md +123 -0
- package/dist/skills/jira/recipes/assign-issue.md +157 -0
- package/dist/skills/jira/recipes/create-issue.md +274 -0
- package/dist/skills/jira/recipes/get-issue-details.md +154 -0
- package/dist/skills/jira/recipes/list-projects.md +151 -0
- package/dist/skills/jira/recipes/my-issues.md +180 -0
- package/dist/skills/jira/recipes/search-issues.md +215 -0
- package/dist/skills/jira/recipes/transition-issue.md +154 -0
- package/dist/skills/jira/recipes/troubleshooting.md +387 -0
- package/dist/skills/knowledge-base/SKILL.md +289 -0
- package/dist/skills/media-tools/SKILL.md +204 -0
- package/dist/skills/media-tools/references/encode-runbook.md +24 -0
- package/dist/skills/media-tools/references/resolve-binaries.md +88 -0
- package/dist/skills/media-tools/scripts/macos/ff-launch.sh +22 -0
- package/dist/skills/media-tools/scripts/macos/ff-poll.sh +10 -0
- package/dist/skills/media-tools/scripts/windows/ff-launch.ps1 +34 -0
- package/dist/skills/media-tools/scripts/windows/ff-poll.ps1 +20 -0
- package/dist/skills/office-download/SKILL.md +161 -0
- package/dist/skills/outlook-365/SKILL.macos.md +331 -0
- package/dist/skills/outlook-365/SKILL.md +171 -0
- package/dist/skills/outlook-365/SKILL.windows.md +124 -0
- package/dist/skills/outlook-365/api/bulk-email-operations.md +178 -0
- package/dist/skills/outlook-365/api/check-availability.md +87 -0
- package/dist/skills/outlook-365/api/create-inbox-rule.md +182 -0
- package/dist/skills/outlook-365/api/download-attachments.md +149 -0
- package/dist/skills/outlook-365/api/find-and-email-contact.md +185 -0
- package/dist/skills/outlook-365/api/manage-calendar-events.md +189 -0
- package/dist/skills/outlook-365/api/organize-with-folders.md +178 -0
- package/dist/skills/outlook-365/api/reply-to-conversation.md +68 -0
- package/dist/skills/outlook-365/api/schedule-meeting.md +73 -0
- package/dist/skills/outlook-365/api/search-and-read-email.md +93 -0
- package/dist/skills/outlook-365/api/send-email-with-attachments.md +94 -0
- package/dist/skills/outlook-365/api/send-email.md +396 -0
- package/dist/skills/outlook-365/api/set-out-of-office.md +196 -0
- package/dist/skills/outlook-365/macos/scripts/bulk-operations.applescript +429 -0
- package/dist/skills/outlook-365/macos/scripts/calendar.applescript +642 -0
- package/dist/skills/outlook-365/macos/scripts/contacts.applescript +635 -0
- package/dist/skills/outlook-365/macos/scripts/helpers.applescript +227 -0
- package/dist/skills/outlook-365/macos/scripts/read-emails.applescript +299 -0
- package/dist/skills/outlook-365/macos/scripts/search-emails.applescript +339 -0
- package/dist/skills/outlook-365/macos/scripts/send-email.applescript +245 -0
- package/dist/skills/outlook-365/uia/BASIC_OPERATIONS.md +278 -0
- package/dist/skills/outlook-365/uia/CALENDAR_OPERATIONS.md +386 -0
- package/dist/skills/outlook-365/uia/COMPOSE_EMAIL.md +426 -0
- package/dist/skills/outlook-365/uia/README.md +75 -0
- package/dist/skills/outlook-365/windows/com/bulk-operations.ps1 +241 -0
- package/dist/skills/outlook-365/windows/com/calendar.ps1 +227 -0
- package/dist/skills/outlook-365/windows/com/contacts.ps1 +270 -0
- package/dist/skills/outlook-365/windows/com/helpers.ps1 +158 -0
- package/dist/skills/outlook-365/windows/com/read-emails.ps1 +115 -0
- package/dist/skills/outlook-365/windows/com/search-emails.ps1 +141 -0
- package/dist/skills/outlook-365/windows/com/send-email.ps1 +121 -0
- package/dist/skills/pdf-architect/SKILL.md +640 -0
- package/dist/skills/powerpoint-architect/SKILL.macos.md +271 -0
- package/dist/skills/powerpoint-architect/SKILL.md +853 -0
- package/dist/skills/powerpoint-architect/SKILL.windows.md +458 -0
- package/dist/skills/powerpoint-architect/custom_themes.md +141 -0
- package/dist/skills/powerpoint-architect/editing-guide.md +424 -0
- package/dist/skills/powerpoint-architect/generator-reference.md +668 -0
- package/dist/skills/powerpoint-architect/images-guide.md +207 -0
- package/dist/skills/powerpoint-architect/issue-fix-mapping.md +768 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-html-to-slide.applescript +389 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-slide.applescript +255 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-speaker-notes.applescript +132 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-text.applescript +245 -0
- package/dist/skills/powerpoint-architect/macos/scripts/apply-slide-layout.applescript +80 -0
- package/dist/skills/powerpoint-architect/macos/scripts/apply-theme.applescript +122 -0
- package/dist/skills/powerpoint-architect/macos/scripts/autofit-placeholders.applescript +62 -0
- package/dist/skills/powerpoint-architect/macos/scripts/close-presentation.applescript +24 -0
- package/dist/skills/powerpoint-architect/macos/scripts/copy-slides.applescript +303 -0
- package/dist/skills/powerpoint-architect/macos/scripts/create-chart-with-data.applescript +305 -0
- package/dist/skills/powerpoint-architect/macos/scripts/create-with-theme.applescript +56 -0
- package/dist/skills/powerpoint-architect/macos/scripts/delete-slides.applescript +137 -0
- package/dist/skills/powerpoint-architect/macos/scripts/export-presentation.applescript +100 -0
- package/dist/skills/powerpoint-architect/macos/scripts/extract-slide-data.applescript +138 -0
- package/dist/skills/powerpoint-architect/macos/scripts/format-shape.applescript +192 -0
- package/dist/skills/powerpoint-architect/macos/scripts/format-slide-content.applescript +336 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-current-slide-number.applescript +38 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-file-path.applescript +94 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-layout-elements.applescript +141 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-layouts.applescript +58 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-opened-files.applescript +50 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-presentation-info.applescript +150 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-recent-files.applescript +68 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-slide-count.applescript +37 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-slide-info.applescript +105 -0
- package/dist/skills/powerpoint-architect/macos/scripts/health-check.applescript +690 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-shape.applescript +188 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-table.applescript +112 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-text-box.applescript +225 -0
- package/dist/skills/powerpoint-architect/macos/scripts/manage-image.applescript +486 -0
- package/dist/skills/powerpoint-architect/macos/scripts/maximize-window.applescript +48 -0
- package/dist/skills/powerpoint-architect/macos/scripts/navigate-to-slide.applescript +84 -0
- package/dist/skills/powerpoint-architect/macos/scripts/open-presentation.applescript +38 -0
- package/dist/skills/powerpoint-architect/macos/scripts/reorder-slides.applescript +106 -0
- package/dist/skills/powerpoint-architect/macos/scripts/replace-text.applescript +193 -0
- package/dist/skills/powerpoint-architect/macos/scripts/save-presentation.applescript +54 -0
- package/dist/skills/powerpoint-architect/macos/scripts/set-animation.applescript +203 -0
- package/dist/skills/powerpoint-architect/macos/scripts/set-transition.applescript +130 -0
- package/dist/skills/powerpoint-architect/visual-styling-guide.md +206 -0
- package/dist/skills/powerpoint-architect/windows/api/advanced.md +317 -0
- package/dist/skills/powerpoint-architect/windows/api/basic.md +392 -0
- package/dist/skills/powerpoint-architect/windows/examples/10-slide-presentation.md +140 -0
- package/dist/skills/powerpoint-architect/windows/examples/custom-theme-workflow.md +219 -0
- package/dist/skills/powerpoint-architect/windows/examples/level-1-workflows.md +531 -0
- package/dist/skills/powerpoint-architect/windows/examples/level-2-scripting.md +239 -0
- package/dist/skills/powerpoint-architect/windows/scripts/create-with-theme.ps1 +81 -0
- package/dist/skills/project-task-list/SKILL.md +174 -0
- package/dist/skills/slack-operation/SKILL.md +97 -0
- package/dist/skills/slack-operation/api/advanced-api/GUIDE.md +277 -0
- package/dist/skills/slack-operation/api/search-and-read/EXAMPLE.md +75 -0
- package/dist/skills/slack-operation/api/search-and-read/GUIDE.md +108 -0
- package/dist/skills/slack-operation/api/send-message/EXAMPLE.md +112 -0
- package/dist/skills/slack-operation/api/send-message/GUIDE.md +63 -0
- package/dist/skills/slack-operation/api/share-files/EXAMPLE.md +94 -0
- package/dist/skills/slack-operation/api/share-files/GUIDE.md +63 -0
- package/dist/skills/slack-operation/ui/desktop-automation/GUIDE.md +55 -0
- package/dist/skills/system-diagnostics/SKILL.md +263 -0
- package/dist/skills/teams-operation/SKILL.md +79 -0
- package/dist/skills/teams-operation/api/advanced-api/GUIDE.md +234 -0
- package/dist/skills/teams-operation/api/meetings/EXAMPLE.md +63 -0
- package/dist/skills/teams-operation/api/meetings/GUIDE.md +52 -0
- package/dist/skills/teams-operation/api/search-and-read/EXAMPLE.md +72 -0
- package/dist/skills/teams-operation/api/search-and-read/GUIDE.md +54 -0
- package/dist/skills/teams-operation/api/send-message/EXAMPLE.md +92 -0
- package/dist/skills/teams-operation/api/send-message/GUIDE.md +60 -0
- package/dist/skills/teams-operation/ui/desktop-automation/GUIDE.md +66 -0
- package/dist/skills/transcribe-media/SKILL.md +142 -0
- package/dist/skills/uipath-integrations/SKILL.md +370 -0
- package/dist/skills/uipath-integrations/reference/connectors.md +331 -0
- package/dist/skills/uipath-integrations/reference/endpoints.md +220 -0
- package/dist/skills/uipath-integrations/reference/errors.md +211 -0
- package/dist/skills/uipath-integrations/reference/metadata.md +317 -0
- package/dist/skills/uipath-integrations/reference/operations.md +297 -0
- package/dist/skills/uipath-orchestrator/SKILL.md +312 -0
- package/dist/skills/uipath-orchestrator/recipes/assets.md +282 -0
- package/dist/skills/uipath-orchestrator/recipes/audit-logs.md +215 -0
- package/dist/skills/uipath-orchestrator/recipes/buckets.md +205 -0
- package/dist/skills/uipath-orchestrator/recipes/jobs.md +286 -0
- package/dist/skills/uipath-orchestrator/recipes/list-folders.md +207 -0
- package/dist/skills/uipath-orchestrator/recipes/queue-items.md +292 -0
- package/dist/skills/uipath-orchestrator/recipes/queues.md +232 -0
- package/dist/skills/uipath-orchestrator/recipes/releases.md +212 -0
- package/dist/skills/uipath-orchestrator/recipes/robots-sessions.md +274 -0
- package/dist/skills/uipath-orchestrator/recipes/schedules.md +280 -0
- package/dist/skills/uipath-orchestrator/reference/endpoints.md +85 -0
- package/dist/skills/uipath-orchestrator/reference/schemas.md +153 -0
- package/dist/skills/uipath-taskautomation/SKILL.md +310 -0
- package/dist/skills/uipath-taskautomation/assets/CodedWorkflow.template.cs +98 -0
- package/dist/skills/uipath-taskautomation/assets/ExampleWorkflow.cs +146 -0
- package/dist/skills/uipath-taskautomation/references/action-activity-map.json +32 -0
- package/dist/skills/uipath-taskautomation/references/action-activity-map.md +44 -0
- package/dist/skills/uipath-taskautomation/references/app-profiles.md +63 -0
- package/dist/skills/uipath-taskautomation/references/automation-spec.md +88 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/before-after-hooks-template.md +115 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/codedworkflow-template.md +186 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/helper-utility-template.md +22 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/json-template.md +91 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/testcase-template.md +92 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/cli-reference.md +249 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/codedworkflow-reference.md +275 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/coding-guidelines.md +229 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/inspect-package-guide.md +81 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/integration-service-guide.md +507 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/operations-guide.md +410 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/third-party-packages-guide.md +67 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/data-manipulation-guide.md +110 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/environment-setup.md +194 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/error-handling-guide.md +195 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/powershell-interop-guide.md +57 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/project-structure-guide.md +114 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/project-structure.md +126 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/uia-elements-interaction-guide.md +109 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/validation-guide.md +147 -0
- package/dist/skills/uipath-taskautomation/references/coded-workflow-authoring.md +219 -0
- package/dist/skills/uipath-taskautomation/references/profiling-output.md +80 -0
- package/dist/skills/uipath-taskautomation/references/reliability-guide.md +83 -0
- package/dist/skills/uipath-taskautomation/references/task-automation-cheatsheet.md +272 -0
- package/dist/skills/uipath-taskautomation/references/template-preflight.md +17 -0
- package/dist/skills/uipath-workflow-documenter/SKILL.md +430 -0
- package/dist/skills/uipath-workflow-documenter/layouts/pdd-template.md +265 -0
- package/dist/skills/uipath-workflow-documenter/routines/from-orchestrator.md +11 -0
- package/dist/skills/uipath-workflow-documenter/routines/from-workflow.md +11 -0
- package/dist/skills/word-architect/SKILL.macos.md +147 -0
- package/dist/skills/word-architect/SKILL.md +502 -0
- package/dist/skills/word-architect/SKILL.windows.md +55 -0
- package/dist/skills/word-architect/api/advanced.md +522 -0
- package/dist/skills/word-architect/api/basic.md +378 -0
- package/dist/skills/word-architect/api/expert.md +302 -0
- package/dist/skills/word-architect/generation.md +308 -0
- package/dist/skills/word-architect/layouts/01-professional.md +168 -0
- package/dist/skills/word-architect/layouts/02-educational-kids.md +354 -0
- package/dist/skills/word-architect/layouts/03-academic.md +83 -0
- package/dist/skills/word-architect/layouts/04-creative.md +242 -0
- package/dist/skills/word-architect/layouts/05-operational.md +94 -0
- package/dist/skills/word-architect/macos/scripts/apply-heading-style.applescript +215 -0
- package/dist/skills/word-architect/macos/scripts/apply-style.applescript +272 -0
- package/dist/skills/word-architect/macos/scripts/autofit-tables.applescript +53 -0
- package/dist/skills/word-architect/macos/scripts/close-document.applescript +287 -0
- package/dist/skills/word-architect/macos/scripts/create-chart-with-data.applescript +379 -0
- package/dist/skills/word-architect/macos/scripts/create-chart.applescript +191 -0
- package/dist/skills/word-architect/macos/scripts/delete-selection.applescript +223 -0
- package/dist/skills/word-architect/macos/scripts/export-document.applescript +167 -0
- package/dist/skills/word-architect/macos/scripts/extract-table.applescript +168 -0
- package/dist/skills/word-architect/macos/scripts/find-by-style.applescript +173 -0
- package/dist/skills/word-architect/macos/scripts/find-text.applescript +199 -0
- package/dist/skills/word-architect/macos/scripts/format-table.applescript +234 -0
- package/dist/skills/word-architect/macos/scripts/format-text.applescript +431 -0
- package/dist/skills/word-architect/macos/scripts/get-document-properties.applescript +95 -0
- package/dist/skills/word-architect/macos/scripts/get-document-structure.applescript +371 -0
- package/dist/skills/word-architect/macos/scripts/get-header-footer-text.applescript +106 -0
- package/dist/skills/word-architect/macos/scripts/get-images.applescript +166 -0
- package/dist/skills/word-architect/macos/scripts/get-opened-files.applescript +103 -0
- package/dist/skills/word-architect/macos/scripts/get-paragraph-bounds.applescript +133 -0
- package/dist/skills/word-architect/macos/scripts/get-paragraph-format.applescript +134 -0
- package/dist/skills/word-architect/macos/scripts/get-recent-files.applescript +82 -0
- package/dist/skills/word-architect/macos/scripts/get-styled-text.applescript +256 -0
- package/dist/skills/word-architect/macos/scripts/get-tables.applescript +126 -0
- package/dist/skills/word-architect/macos/scripts/get-text-formatting.applescript +224 -0
- package/dist/skills/word-architect/macos/scripts/get-text.applescript +383 -0
- package/dist/skills/word-architect/macos/scripts/get-theme-colors.applescript +123 -0
- package/dist/skills/word-architect/macos/scripts/health-check.applescript +606 -0
- package/dist/skills/word-architect/macos/scripts/insert-cover-page.applescript +77 -0
- package/dist/skills/word-architect/macos/scripts/insert-header-footer.applescript +87 -0
- package/dist/skills/word-architect/macos/scripts/insert-horizontal-line.applescript +112 -0
- package/dist/skills/word-architect/macos/scripts/insert-html.applescript +440 -0
- package/dist/skills/word-architect/macos/scripts/insert-hyperlink.applescript +191 -0
- package/dist/skills/word-architect/macos/scripts/insert-image.applescript +320 -0
- package/dist/skills/word-architect/macos/scripts/insert-list.applescript +317 -0
- package/dist/skills/word-architect/macos/scripts/insert-pagebreak.applescript +181 -0
- package/dist/skills/word-architect/macos/scripts/insert-smartart.applescript +104 -0
- package/dist/skills/word-architect/macos/scripts/insert-table.applescript +238 -0
- package/dist/skills/word-architect/macos/scripts/insert-text.applescript +677 -0
- package/dist/skills/word-architect/macos/scripts/insert-textbox.applescript +261 -0
- package/dist/skills/word-architect/macos/scripts/maximize-window.applescript +67 -0
- package/dist/skills/word-architect/macos/scripts/normalize-formatting.applescript +56 -0
- package/dist/skills/word-architect/macos/scripts/open-document.applescript +222 -0
- package/dist/skills/word-architect/macos/scripts/replace-text.applescript +390 -0
- package/dist/skills/word-architect/macos/scripts/save-document.applescript +230 -0
- package/dist/skills/word-architect/macos/scripts/select-range.applescript +142 -0
- package/dist/skills/word-architect/macos/scripts/set-document-properties.applescript +195 -0
- package/dist/skills/word-architect/macos/scripts/set-page-layout.applescript +273 -0
- package/dist/skills/word-architect/macos/scripts/set-theme-colors.applescript +264 -0
- package/dist/skills/word-architect/macos/scripts/undo-redo.applescript +61 -0
- package/dist/skills/word-architect/macos/scripts/update-toc.applescript +112 -0
- package/dist/skills/word-architect/reference/formatting.md +119 -0
- package/dist/skills/word-architect/reference/html-layouts/01-executive-summary-box.md +36 -0
- package/dist/skills/word-architect/reference/html-layouts/02-kpi-summary-table.md +68 -0
- package/dist/skills/word-architect/reference/html-layouts/03-comparison-table.md +63 -0
- package/dist/skills/word-architect/reference/html-layouts/04-pros-cons-table.md +86 -0
- package/dist/skills/word-architect/reference/html-layouts/05-timeline-table.md +114 -0
- package/dist/skills/word-architect/reference/html-layouts/06-raci-matrix.md +95 -0
- package/dist/skills/word-architect/reference/html-layouts/07-data-table-alternating.md +84 -0
- package/dist/skills/word-architect/reference/html-layouts/08-callout-box.md +102 -0
- package/dist/skills/word-architect/reference/html-layouts/09-vertical-milestone.md +100 -0
- package/dist/skills/word-architect/reference/quality-assurance.md +102 -0
- package/dist/skills/word-architect/reference/tables.md +62 -0
- package/dist/skills/word-architect/reference/tracked-changes.md +34 -0
- package/dist/skills/word-architect/reference/uia-fallback.md +231 -0
- package/dist/skills/word-architect/reference/visual-elements.md +82 -0
- package/dist/skills/word-architect/windows/scripts/apply-heading-style.ps1 +190 -0
- package/dist/skills/word-architect/windows/scripts/autofit-tables.ps1 +64 -0
- package/dist/skills/word-architect/windows/scripts/create-chart-with-data.ps1 +133 -0
- package/dist/skills/word-architect/windows/scripts/create-chart.ps1 +73 -0
- package/dist/skills/word-architect/windows/scripts/export-document.ps1 +86 -0
- package/dist/skills/word-architect/windows/scripts/get-current-file.ps1 +27 -0
- package/dist/skills/word-architect/windows/scripts/insert-cover-page.ps1 +79 -0
- package/dist/skills/word-architect/windows/scripts/insert-horizontal-line.ps1 +74 -0
- package/dist/skills/word-architect/windows/scripts/insert-image.ps1 +98 -0
- package/dist/skills/word-architect/windows/scripts/insert-smartart.ps1 +118 -0
- package/dist/skills/word-architect/windows/scripts/insert-text-box.ps1 +90 -0
- package/dist/skills/word-architect/windows/scripts/normalize-formatting.ps1 +63 -0
- package/package.json +5 -4
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
# Recording Processing
|
|
2
|
+
|
|
3
|
+
User supplies a screen recording in Phase 1 (attached via AskUser, or an existing file on disk; `.mp4`, `.mov`, `.avi`, `.mkv`, `.webm`). **Always extract frames** — PDD §3.2 needs them. Audio is optional and usually absent: a silent recording is complete input. When there is speech, the transcript drives narrative; frames are pulled either way.
|
|
4
|
+
|
|
5
|
+
## Recording Folder Layout
|
|
6
|
+
|
|
7
|
+
A recorder-produced attended folder contains:
|
|
8
|
+
|
|
9
|
+
- `video/d0.mp4`: screen capture, with optional audio
|
|
10
|
+
- `trace/actions.ndjson`: one JSON action per line; `tMs` is milliseconds since recording start
|
|
11
|
+
- `trace/img/`: action images; resolve each row's nullable `ImagePath` relative to the recording folder
|
|
12
|
+
|
|
13
|
+
Legacy folders instead contain `video.mp4`, `data.json` (a JSON action array) and root-level images. Inspect the folder once and use the existing files without rewriting them. Preserve absolute image paths; resolve relative ones against the recording folder.
|
|
14
|
+
|
|
15
|
+
Read what you need with `ReadFile`. Transcripts are analysis outputs, not recorder files.
|
|
16
|
+
|
|
17
|
+
## Get a transcript
|
|
18
|
+
|
|
19
|
+
Three cases:
|
|
20
|
+
|
|
21
|
+
1. **Recorder folder has `transcript.json`** — use it directly.
|
|
22
|
+
2. **No transcript** — invoke `transcribe-media` with the discovered video path or the supplied standalone video. Returns one `transcript.md` (≤5 min) or a folder of `chunk_NNN.md` files (>5 min); `[mm:ss] text` lines either way. Don't shell out to ffmpeg for audio yourself; the skill handles chunking and retry.
|
|
23
|
+
3. **No audio track** — `transcribe-media` returns HTTP 422 (`No audio track`). Normal for a recording made without audio, not an error: don't tell the user audio is missing. Skip the transcript and use the Scene-detection fallback below.
|
|
24
|
+
|
|
25
|
+
`transcript.json` and the transcribe-media output (`transcript.md` or the chunk folder) feed the same downstream step: read end to end, pick timestamps where the speaker references UI ("here", "this column", "click on", "as you can see"), names a screen, or marks a step boundary.
|
|
26
|
+
|
|
27
|
+
## Long recordings: split, fan out, stitch
|
|
28
|
+
|
|
29
|
+
Trigger: recording longer than ~10 min, or a transcript that covers several sub-processes. Never work it in one pass.
|
|
30
|
+
|
|
31
|
+
1. **Split.** Cut the transcript into sub-processes at the speaker's boundaries (new screen, system, or "next we…"). Before any extraction, write the table to `<wiki>/raw/segments/<basename>/index.md`: `# | Sub-process | Start | End | Transcript chunks`. Ranges contiguous, no gaps. Don't ask the user to confirm the split.
|
|
32
|
+
2. **Fan out.** One `Agent` per row (`agent_type: "general"`, `fork: false`), all in one turn so they run in parallel. Prompt: the video path, the row's range, its transcript files, this guide's absolute path, and the output file `<wiki>/raw/segments/<basename>/<NN>-<slug>.md`. No `Agent` tool → work the rows yourself, one by one, same output.
|
|
33
|
+
3. **Per segment** (the agent): only its range. Frames per *Extract frames* below, at absolute timestamps from the original video. Steps, business rules, decisions (`Step | Condition | Action`), open items → its output file. It never asks the user.
|
|
34
|
+
4. **`analyze-video` per segment**, never on the whole file. Cut the range into its own folder (stream copy; `.mkv` takes any source codec):
|
|
35
|
+
|
|
36
|
+
```bash
|
|
37
|
+
mkdir -p "$TMPDIR/<basename>-segments/<NN>"
|
|
38
|
+
ffmpeg -ss <start> -to <end> -i "<video>" -c copy "$TMPDIR/<basename>-segments/<NN>/video.mkv"
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
```powershell
|
|
42
|
+
New-Item -ItemType Directory -Force "$env:TEMP\<basename>-segments\<NN>" | Out-Null
|
|
43
|
+
ffmpeg -ss <start> -to <end> -i "<video>" -c copy "$env:TEMP\<basename>-segments\<NN>\video.mkv"
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
Call it with `video_path` = the cut file and `recording_path` = its folder; `video_workflow.json` lands there. A shared folder overwrites the other segments' output. Its times are segment-relative: add the row's start. 422 "segments of at most N min" → cut that range into N-minute pieces and analyze each.
|
|
47
|
+
5. **Stitch** in table order once every agent returns: steps → `as-is/steps/`, rules → `as-is/business-rules.md`, exceptions → `as-is/exception-handling.md`, open items → `queries/open-questions.md`. Merge a step split across a boundary into one; keep timestamps absolute.
|
|
48
|
+
|
|
49
|
+
## Extract frames at picked timestamps
|
|
50
|
+
|
|
51
|
+
Bash:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
ffmpeg -ss <HH:MM:SS> -i "<video>" -vframes 1 -vf "scale='min(1400,iw)':-2" -q:v 2 "<wiki>/raw/screenshots/<basename>/<descriptive-name>.png"
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
PowerShell (Windows):
|
|
58
|
+
|
|
59
|
+
```powershell
|
|
60
|
+
ffmpeg -ss <HH:MM:SS> -i "<video>" -vframes 1 -vf "scale='min(1400,iw)':-2" -q:v 2 "<wiki>\raw\screenshots\<basename>\<descriptive-name>.png"
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Save under `<wiki>/raw/screenshots/<recording-basename>/`. Filename ties to content (`oleeo-candidate-view.png`), never `frame-0042.png`. Reference frames by relative path in `as-is/steps/*.md` and entity pages so PDD pre-flight just inventories.
|
|
64
|
+
|
|
65
|
+
## Scene-detection fallback
|
|
66
|
+
|
|
67
|
+
Only for a silent recording (`transcribe-media` returned 422) — no speech to anchor on. Bash:
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
ffmpeg -i "<video>" -vf "select='gt(scene,0.3)',scale='min(1400,iw)':-2" -vsync vfr -q:v 2 "<wiki>/raw/screenshots/<basename>/scene_%04d.png"
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
PowerShell (Windows):
|
|
74
|
+
|
|
75
|
+
```powershell
|
|
76
|
+
ffmpeg -i "<video>" -vf "select='gt(scene,0.3)',scale='min(1400,iw)':-2" -vsync vfr -q:v 2 "<wiki>\raw\screenshots\<basename>\scene_%04d.png"
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
One frame per significant visual change. Cap ~50; if more, raise the threshold (`gt(scene,0.4)`).
|
|
80
|
+
|
|
81
|
+
`-ss` before `-i` seeks straight to the time instead of decoding the video up to it; keep that order. Frames are capped at 1400 px wide (`scale='min(1400,iw)':-2`): every model sees them unresized, so pixel boxes read off a frame match the file.
|
|
82
|
+
|
|
83
|
+
## Choosing and reading frames
|
|
84
|
+
|
|
85
|
+
- Candidates come from three sources: transcript cues, scene changes inside each step's time range, and the last second before each submit, save or page change. Silent clicks have no cue; scene changes catch them. Typing changes too few pixels to cut a scene, so fields filled just before a submit appear only in that last frame.
|
|
86
|
+
- Scene-change candidates per step range. Start at `gt(scene,0.1)`; raise toward `0.2` if a step yields too many. Bash:
|
|
87
|
+
|
|
88
|
+
```bash
|
|
89
|
+
ffmpeg -ss <HH:MM:SS> -to <HH:MM:SS> -i "<video>" -vf "select='gt(scene,0.1)',scale='min(1400,iw)':-2" -vsync vfr -q:v 2 "<wiki>/raw/screenshots/<basename>/<step>-cand_%02d.png"
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
PowerShell (Windows):
|
|
93
|
+
|
|
94
|
+
```powershell
|
|
95
|
+
ffmpeg -ss <HH:MM:SS> -to <HH:MM:SS> -i "<video>" -vf "select='gt(scene,0.1)',scale='min(1400,iw)':-2" -vsync vfr -q:v 2 "<wiki>\raw\screenshots\<basename>\<step>-cand_%02d.png"
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
- `scdet` is an alternative detector. Delete candidates you do not keep.
|
|
99
|
+
- **One frame pass.** Extract the candidates for your whole range once and pick from a contact sheet; read at full size only the frames you choose (one per step, plus a crop for small text). A step whose candidates miss a value it cites gets one targeted grab at a few timestamps; still missing → transcript-only and an open item. Never sweep the range again: re-extracting is what makes a long recording slow.
|
|
100
|
+
- Pick the frame where the action has completed: dialog open, value visible, menu expanded. Not the frame before the click.
|
|
101
|
+
- A contact sheet only helps choose between candidates. It is never the frame you read.
|
|
102
|
+
- Read each chosen frame on its own with `ReadFile`, at full size. Never downscale a frame for reading.
|
|
103
|
+
- Small text, or a label you cannot read: crop at source resolution from the video, not from a downscaled frame. `<w>:<h>:<x>:<y>` are source pixels. Bash:
|
|
104
|
+
|
|
105
|
+
```bash
|
|
106
|
+
ffmpeg -ss <HH:MM:SS> -i "<video>" -vframes 1 -vf "crop=<w>:<h>:<x>:<y>" -q:v 2 "<wiki>/raw/screenshots/<basename>/<descriptive-name>-crop.png"
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
PowerShell (Windows):
|
|
110
|
+
|
|
111
|
+
```powershell
|
|
112
|
+
ffmpeg -ss <HH:MM:SS> -i "<video>" -vframes 1 -vf "crop=<w>:<h>:<x>:<y>" -q:v 2 "<wiki>\raw\screenshots\<basename>\<descriptive-name>-crop.png"
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
- Quote labels, field names, menu items, and file names exactly as on screen: case, punctuation, order.
|
|
116
|
+
- Mark facts that come only from the transcript as `transcript-only`. If a label is still unreadable after cropping, say so; do not guess it.
|
|
117
|
+
|
|
118
|
+
## Callouts and masking (user choice)
|
|
119
|
+
|
|
120
|
+
Asked once per project, in the PDD phase's ask (`pdd-generation.md` → Process metadata) — one single-choice question with these four options, labels word for word, the same as the task route:
|
|
121
|
+
|
|
122
|
+
- **Mask sensitive data + add numbered callouts** — both of the below.
|
|
123
|
+
- **Add numbered callouts only** — red box, numbered badge and short label on the element each step acts on.
|
|
124
|
+
- **Mask sensitive data only** — solid fill over credentials, bank or card account numbers, personal emails and phone numbers, person names, avatars.
|
|
125
|
+
- **Leave frames as recorded** — neither; frames stay unaltered.
|
|
126
|
+
|
|
127
|
+
When frames show such data, the masking option's label ends with "(Recommended)"; mask only when chosen. Say in the question that either one adds time, since every step's frame is boxed and checked. Record the answer in `<wiki>/raw/screenshots/annotation.md` (`callouts: yes|no`, `masking: yes|no`). Later turns and re-exports follow it; never re-ask.
|
|
128
|
+
|
|
129
|
+
At PDD pre-flight, when either is chosen:
|
|
130
|
+
|
|
131
|
+
1. Once per session, call `/image/box-format`. It names the box field your model gives most accurately (`box` in pixels, or `box_2d` normalized and y-first); use that field for every box.
|
|
132
|
+
2. Per frame the PDD embeds: `ReadFile` the raw frame, then box each element the step acts on, tight to the element's own border (the field, button, cell or link, not its row or panel). Labels ≤ 5 words. With masking on, box as a redaction every item on the mask list (passwords and secrets, card numbers, bank account and routing numbers, personal emails and phone numbers, a person's name, face or avatar) and nothing on the keep list (account codes and names, company names, document, invoice, batch, ledger, customer and vendor numbers, amounts, dates): the step text cites them. An item on both lists is masked: a customer or vendor who is a person (a sole trader) is a person's name.
|
|
133
|
+
3. One `ExecuteSkillApi` call per frame (`box` shown):
|
|
134
|
+
|
|
135
|
+
```json
|
|
136
|
+
{ "operations": [{ "endpoint": "/image/annotate", "body": { "imagePath": "<wiki>/raw/screenshots/<basename>/<name>.png", "outputPath": "<wiki>/raw/screenshots/<basename>/annotated/<name>.png", "callouts": [{ "box": [612, 301, 790, 327], "label": "Ending balance" }], "redactions": [{ "box": [96, 410, 260, 432] }] } }], "toolName": "Screenshots", "description": "Marking up the step screenshot" }
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
Callouts number 1..n in array order; the result lists them (`callouts`: `n`, `label`). Cite them by those numbers and labels in the PDD step text. Masking only → `redactions` alone.
|
|
140
|
+
4. Check the proof the call returns. Check every numbered box against its step text in its crop: it sits on the exact row, field or button named. A box on a neighbour, a label covering the value, or a face or personal data still visible → re-measure that box on the raw frame, never on the proof, and re-run on the raw frame, never on an annotated one. Read values for the step text off the raw frame too: a box border can hide a minus sign or a digit.
|
|
141
|
+
|
|
142
|
+
The PDD embeds the annotated frame; keep the raw one.
|
|
143
|
+
|
|
144
|
+
## After Extraction
|
|
145
|
+
|
|
146
|
+
Walk frames alongside the transcript, when there is one, and the action trace. Use them to ground entity/step capture. Don't ask the user about UI details visible in a frame. Do ask what the recording cannot show: off-screen decisions, business rules behind choices, exception paths, volumes. Classify these gaps via the interview spine before asking.
|
|
147
|
+
|
|
148
|
+
Don't extract twice. Check `<wiki>/raw/screenshots/<basename>/` exists first.
|
|
149
|
+
|
|
150
|
+
## Structured Step Extraction
|
|
151
|
+
|
|
152
|
+
For step-level extraction beyond frame grabs, call `ExecuteSkillApi` `/recorded-task/analyze-recording` with `session_id` and `recording_path` set to the recording folder; it saves `merged_workflow.json` there. **Never pass `local_skills_path`** — we want wiki content, not a routine. Ingest the workflow into `as-is/steps/`, `entities/applications/`, `entities/artifacts/`.
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
# Automation Hub publish over `SendUiPathRequest`
|
|
2
|
+
|
|
3
|
+
The fallback transport for `automation-hub-publishing.md`, used only when the `uipath-automationhub` skill cannot take its CLI path. Every call here goes through the `SendUiPathRequest` tool — never `curl`, `wget`, or any shell HTTP: the Delegate sandbox denies them, and a shell call fails at DNS with an error that reads like a network policy rather than what it is.
|
|
4
|
+
|
|
5
|
+
## Transport
|
|
6
|
+
|
|
7
|
+
```typescript
|
|
8
|
+
SendUiPathRequest({
|
|
9
|
+
method: "GET", // GET | POST | PATCH
|
|
10
|
+
path: "automationhub_/api/v1/openapi/<endpoint>", // relative — the host prepends base URL, org and tenant
|
|
11
|
+
body: { ... } // JSON object, POST/PATCH only
|
|
12
|
+
})
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
- **Never set `headers`.** Auth is injected by the host and `authorization` is stripped from caller headers. Never add `x-ah-openapi-auth` or `x-ah-openapi-app-key` — they route to the admin-token path and reject the user's cloud token with 401.
|
|
16
|
+
- **Status.** The tool returns the response body, not the HTTP status line. Read AH's own envelope: `statusCode` on the standard wrapper, `status` on the schema call. A non-2xx arrives as a tool error whose text carries the API error body — parse it for `message` / `errorDetails`.
|
|
17
|
+
- **Large responses** past `maxInlineBytes` (default 2KB) are written to a file and previewed. `idea-schema` always exceeds it: pass `maxInlineBytes: -1` or `ReadFile` the dumped file — never work from the preview, which truncates the field catalog.
|
|
18
|
+
- **Document bytes** go via `bodyFromFile: "<absolute path>"` holding the whole JSON body, so base64 never enters the conversation.
|
|
19
|
+
|
|
20
|
+
## Sequence
|
|
21
|
+
|
|
22
|
+
Collect every input before the first write — name, description, category id, `PROCESS_DOCUMENTS` answer code, owner and submitter emails (the signed-in user's, from `automation-hub-publishing.md`), plus any question the live schema flags `required`. Do not discover gaps one 400 at a time.
|
|
23
|
+
|
|
24
|
+
1. **`GET /idea-flows`** — connectivity check and the flow list. Envelope `{ message, statusCode, data: [...] }`. Pick the entry whose `Idea flow name` contains "Business Process" (case-insensitive); keep its `Idea flow ID`. Not-available signals → **Automation Hub not available on this tenant**, then stop.
|
|
25
|
+
2. **`GET /idea-schema?idea_flow_id={id}`** — `data.properties.schema.properties` is the field catalog (Assessment Type › Section › Question, with `required` flags and enum `answer_option` codes); `data.user_inputs` is the body template. **Never POST the template verbatim** — its example values (`OVERVIEW_CATEGORY: 1`, placeholder codes, example emails) are rejected.
|
|
26
|
+
3. **`GET /hierarchy`** → a valid category from `data.categories[]` (nested `subcategories`; only `category_is_active: 1`). **`GET /users?s=<percent-encoded email>`** once per address (owner, then submitter if different) — `s` matches `user_email`, so the reply is the users whose email contains that text; take the entry whose `user_email` equals the *unencoded* address exactly (prefer `user_is_active: 1`). **Percent-encode the address before it goes in the query** (`encodeURIComponent`): the tool concatenates `path` verbatim, and a plus-alias like `alice+delegate@example.com` otherwise arrives as `alice delegate@example.com` — the server decodes `+` as a space — so a valid account reads as unlisted. `+` → `%2B`, `&` → `%26`, `#` → `%23`. Never list users unfiltered: the endpoint pages at 20 by default and a tenant can hold thousands, so a bounded list misses valid accounts. An address with no exact match is unlisted — creating with it 400s with `Cannot identify owner by email`; the handoff's owner rule applies (ask which listed address is theirs, or report that publishing needs their Automation Hub access). Only when the user must pick from the directory, page `GET /users?page=<n>&limit=100` until `page` reaches `totalPages`.
|
|
27
|
+
4. **`POST /idea-from-schema`** with `{ "idea_flow_id": <id>, "user_inputs": { ... } }`. Required for Business Process (owner and submitter are enforced even though the schema does not flag them):
|
|
28
|
+
|
|
29
|
+
| Question | Section | Shape |
|
|
30
|
+
|---|---|---|
|
|
31
|
+
| `OVR-OVERVIEW_NAME` | `ah-section-ovr-0-0` | `{"value": "<name>"}` |
|
|
32
|
+
| `OVR-OVERVIEW_DESCRIPTION` | `ah-section-ovr-0-0` | `{"value": "<desc>"}` |
|
|
33
|
+
| `OVR-OVERVIEW_CATEGORY` | `ah-section-ovr-0-0` | `{"value": <valid id>}` |
|
|
34
|
+
| `OVR-PROCESS_DOCUMENTS` | `ah-section-ovr-0-0` | `{"value": ["<answer_option code>"]}` |
|
|
35
|
+
| `OVR-PROCESS_OWNER` | `ah-section-ovr-0-0` | `"<email>"` (direct string) |
|
|
36
|
+
| `OVR-OVERVIEW_PROCESS_SUBMITTER` | `ah-section-ovr-0-1` | `"<email>"` (direct string) |
|
|
37
|
+
|
|
38
|
+
`statusCode: 201` → read **`data.process_id`** and `data.process_slug` (nested, not top-level). A 201 means the process exists — never re-POST on a missing field read; re-read the response. `400` with `errorDetails: {}` and "Please fill in all the required information" → a required field the API won't name is missing: check owner/submitter, then diff the payload against every `required`-flagged question in the schema. `409` → duplicate name; ask for a new one.
|
|
39
|
+
5. **`POST /automations/{process_id}/documents`** once per document the handoff selected, body in a file. Every field below derives from that selection — its type (`PDD` or `SDD`), the file's own basename and its mimetype — never from a fixed example:
|
|
40
|
+
|
|
41
|
+
```json
|
|
42
|
+
{ "document_title": "<TYPE> - <name>", "document_description": "<desc>", "document_type_id": <1 for PDD, 2 for SDD>,
|
|
43
|
+
"file": { "file_name": "<basename of the selected file, e.g. order-intake-SDD.md>", "mimetype": "<its mimetype from the handoff>",
|
|
44
|
+
"file_content": "<base64 of that file>", "file_encoding": "base64" } }
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
An SDD labelled PDD, or Markdown bytes under a `.docx` name, publishes an attachment Automation Hub mislabels or cannot open. Exactly one of `file` or `embed_link`. `file_encoding` must be the literal `base64`. Read **`data.document_id`**. On a 400, report that document as failed and continue with the rest.
|
|
48
|
+
6. **`GET /automations/{process_id}/documents`** — verify every `document_id` appears under `data.documents[]` before reporting success. Build the links from the same org and tenant the process was created on: `{baseUrl}/{org}/{tenant}/automationhub_/automation-profile/{process_slug}` and `.../{process_slug}/documentation`.
|
|
49
|
+
|
|
50
|
+
## Automation Hub not available on this tenant
|
|
51
|
+
|
|
52
|
+
Two cases with different remedies. Quote the message verbatim and **stop** — no retry, no other tenant.
|
|
53
|
+
|
|
54
|
+
- **Not enabled** — a 404 whose body says `not found in organization`, or a redirect toward `portal_/unregistered`: *"Please contact your administrator to enable Automation Hub on this tenant."*
|
|
55
|
+
- **Never onboarded** — `422 Tenant Lookup Error` on every call: *"Automation Hub is reachable for this tenant but has not finished setup. Open Automation Hub in the browser once to complete it, then retry."*
|
|
56
|
+
|
|
57
|
+
The tool may not expose a redirect target, so classify by these body signals rather than by status number.
|
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
# Case Definition Vocabulary
|
|
2
|
+
|
|
3
|
+
Domain knowledge for authoring the §1 Case Definition in an SDD. Covers the 9 closed task types, variable categories and types, binding forms, and the rule-context matrix.
|
|
4
|
+
|
|
5
|
+
**Scope:** This document contains the CONTENT half of Composer's case definition spec — the vocabulary and structural rules needed to author an SDD. It does NOT include orchestration mechanics (`case_design_plan.json`, `validate-sdd`, tenant ID resolution, Case Designer import/export, `review_items.json`). Those are Composer-internal and are never produced by this skill (see Appendix §F fence).
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## Variable Categories
|
|
10
|
+
|
|
11
|
+
| Category | Meaning |
|
|
12
|
+
|---|---|
|
|
13
|
+
| Input | Value that enters the case from the trigger (form, API, document) |
|
|
14
|
+
| Output | Value the case produces on completion (decision, document, result) |
|
|
15
|
+
| Intermediate | Value computed or derived during case execution |
|
|
16
|
+
| System | Platform-assigned metadata (case ID, created-at timestamp, current stage) |
|
|
17
|
+
|
|
18
|
+
## Variable Types
|
|
19
|
+
|
|
20
|
+
| Type | Examples |
|
|
21
|
+
|---|---|
|
|
22
|
+
| Text | Name, description, status label, free-form string |
|
|
23
|
+
| Number | Amount, count, score, percentage |
|
|
24
|
+
| Boolean | Approved/rejected flag, completed flag |
|
|
25
|
+
| Date | Submission date, deadline, SLA due-by |
|
|
26
|
+
| Collection | List of items, set of document pages, array of approvers |
|
|
27
|
+
| File | Document, attachment, image |
|
|
28
|
+
|
|
29
|
+
## Binding Forms
|
|
30
|
+
|
|
31
|
+
Bindings reference case variables using backtick notation in the SDD:
|
|
32
|
+
|
|
33
|
+
| Form | Example | Meaning |
|
|
34
|
+
|---|---|---|
|
|
35
|
+
| Case variable | `` `case.applicationId` `` | Top-level case variable |
|
|
36
|
+
| Stage output | `` `stage.ReviewAndApproval.approvalDecision` `` | Output of a stage |
|
|
37
|
+
| Task output | `` `task.ExtractData.extractedAmount` `` | Output of a specific task |
|
|
38
|
+
| Constants | `` `"APPROVED"` `` | Literal value |
|
|
39
|
+
|
|
40
|
+
Unresolved bindings (connection IDs, activity type IDs, action app IDs not yet provisioned) always render as `—`. Never fabricate a platform-specific identifier.
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## Rule-Context Matrix
|
|
45
|
+
|
|
46
|
+
Summarizes where each rule type applies in a Maestro case:
|
|
47
|
+
|
|
48
|
+
| Rule Type | Applies At | Example |
|
|
49
|
+
|---|---|---|
|
|
50
|
+
| Entry condition | Stage entry | Case variable equals expected value |
|
|
51
|
+
| Completion condition | Stage or task completion | All required tasks finished |
|
|
52
|
+
| Exit / Exception | Stage or task exit | SLA breach, escalation trigger |
|
|
53
|
+
| SLA | Stage or task | Business days until escalation |
|
|
54
|
+
| Validation | Task I/O | Field must be non-empty, value in range |
|
|
55
|
+
| Assignment | Task | Persona or queue receives the task |
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## 9 Closed Task Types (summary)
|
|
60
|
+
|
|
61
|
+
See `component-type-mapping.md` for the full decision tree.
|
|
62
|
+
|
|
63
|
+
| Type | Short description |
|
|
64
|
+
|---|---|
|
|
65
|
+
| `process` | Human-driven Maestro App worklist task |
|
|
66
|
+
| `action` | Automated in-case action (state change, notification) |
|
|
67
|
+
| `agent` | AI reasoning or decision step |
|
|
68
|
+
| `api-workflow` | Integration Service workflow or REST API call |
|
|
69
|
+
| `rpa` | UiPath Robot-executed workflow |
|
|
70
|
+
| `wait-for-timer` | Time-based pause |
|
|
71
|
+
| `wait-for-connector` | External event wait via connector |
|
|
72
|
+
| `execute-connector-activity` | Direct Integration Service connector activity |
|
|
73
|
+
| `case-management` | Nested Maestro case (sub-case) |
|
|
74
|
+
|
|
75
|
+
`external-agent` is NOT a valid type in the SDD dialect.
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Appendix §F Fence — What This Skill Does NOT Produce
|
|
80
|
+
|
|
81
|
+
The following Composer-internal orchestration artifacts are NEVER authored, read, or written by this skill:
|
|
82
|
+
|
|
83
|
+
- `case_design_plan.json` — Composer's internal case design plan file
|
|
84
|
+
- `review_items.json` — Composer's internal review task list
|
|
85
|
+
- `uip_context.json` — UiPath tenant/connection context file
|
|
86
|
+
- `validate-sdd` output — Composer's validation command output
|
|
87
|
+
- Case Designer `.json` import/export files
|
|
88
|
+
- Tenant ID, connection ID, activity type ID, action app ID values — never fabricated; rendered as `—`
|
|
89
|
+
|
|
90
|
+
Appendix A (Implementation Readiness) in the SDD is SELF-COMPUTED from the authored `solution/` wiki content — it does not import any of the above files.
|
package/dist/skills/business-analysis/references/case-design-patterns/loan-origination-spec.md
ADDED
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Loan Origination — Case Design Reference
|
|
2
|
+
|
|
3
|
+
A reference case design for the loan origination process, illustrating the SDD structure with real-world content. Use as a pattern reference when authoring SDDs for financial services / lending processes.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Case Overview
|
|
8
|
+
|
|
9
|
+
**Process:** Consumer loan origination (personal or mortgage loan application)
|
|
10
|
+
**Trigger:** Applicant submits a loan application (web portal, branch, or API)
|
|
11
|
+
**Primary outcome:** Loan approved with terms and disbursed, or declined with reason
|
|
12
|
+
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
## Stage Model
|
|
16
|
+
|
|
17
|
+
| Stage | Entry Condition | Completion Condition | SLA |
|
|
18
|
+
|---|---|---|---|
|
|
19
|
+
| Application Intake | Case submitted | Application data complete and valid | 1 business day |
|
|
20
|
+
| Document Collection | Intake complete | All required documents received | 3 business days |
|
|
21
|
+
| Credit & Risk Assessment | Documents complete | Credit decision reached | 1 business day |
|
|
22
|
+
| Review & Approval | Assessment complete | Approval decision by authorized officer | 2 business days |
|
|
23
|
+
| Disbursement | Approval granted | Funds transferred to applicant | 1 business day |
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## Key Variables (§1.5 pattern)
|
|
28
|
+
|
|
29
|
+
| Variable | Category | Type | Binding |
|
|
30
|
+
|---|---|---|---|
|
|
31
|
+
| applicantId | Input | Text | `` `case.applicantId` `` |
|
|
32
|
+
| requestedAmount | Input | Number | `` `case.requestedAmount` `` |
|
|
33
|
+
| loanTerm | Input | Number | `` `case.loanTerm` `` |
|
|
34
|
+
| applicantDocuments | Input | Collection | `` `case.applicantDocuments` `` |
|
|
35
|
+
| creditScore | Intermediate | Number | `` `task.RunCreditCheck.creditScore` `` |
|
|
36
|
+
| riskCategory | Intermediate | Text | `` `task.AssessRisk.riskCategory` `` |
|
|
37
|
+
| approvalDecision | Output | Boolean | `` `stage.ReviewAndApproval.approvalDecision` `` |
|
|
38
|
+
| approvedAmount | Output | Number | `` `stage.ReviewAndApproval.approvedAmount` `` |
|
|
39
|
+
| declineReason | Output | Text | `` `stage.ReviewAndApproval.declineReason` `` |
|
|
40
|
+
| disbursedAt | Output | Date | `` `task.DisburseToAccount.disbursedAt` `` |
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## Task Types (§2 pattern)
|
|
45
|
+
|
|
46
|
+
| Task | Type | Notes |
|
|
47
|
+
|---|---|---|
|
|
48
|
+
| ValidateApplication | `action` | Automated field validation on case submission |
|
|
49
|
+
| CollectDocuments | `process` | Loan officer collects and uploads required docs |
|
|
50
|
+
| RunCreditCheck | `api-workflow` | Integration Service call to credit bureau |
|
|
51
|
+
| AssessRisk | `agent` | AI agent scores risk from credit + application data |
|
|
52
|
+
| ReviewApplication | `process` | Underwriter reviews full application package |
|
|
53
|
+
| ApproveOrDecline | `process` | Authorized officer makes final credit decision |
|
|
54
|
+
| SendDecisionNotification | `action` | Automated notification to applicant |
|
|
55
|
+
| DisburseToAccount | `rpa` | Robot workflow transfers funds via banking system |
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Personas (§3 pattern)
|
|
60
|
+
|
|
61
|
+
| Persona | Role | Queue / App View |
|
|
62
|
+
|---|---|---|
|
|
63
|
+
| Loan Officer | Document collection, initial review | Document Collection queue |
|
|
64
|
+
| Underwriter | Full application review | Review queue |
|
|
65
|
+
| Credit Officer | Approval decision | Approval queue |
|
|
66
|
+
| Applicant | Submits application (external; not a Maestro user) | — |
|
|
67
|
+
|
|
68
|
+
---
|
|
69
|
+
|
|
70
|
+
## Integration Pattern (§4)
|
|
71
|
+
|
|
72
|
+
| Integration | Type | Connection ID |
|
|
73
|
+
|---|---|---|
|
|
74
|
+
| Credit Bureau API | `api-workflow` | — |
|
|
75
|
+
| Banking Disbursement System | `rpa` | — |
|
|
76
|
+
| Notification Service | `execute-connector-activity` | — |
|
|
77
|
+
|
|
78
|
+
Connection IDs render as `—` in the SDD until provisioned in the target environment.
|
|
79
|
+
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
## Authoring Notes
|
|
83
|
+
|
|
84
|
+
- `external-agent` is NOT used — the AI risk assessment step maps to `agent`.
|
|
85
|
+
- No `review_items.json`, `case_design_plan.json`, or tenant ID lookup.
|
|
86
|
+
- Appendix A (readiness) counts the `—` cells in the I/O tables — in this reference design, connection IDs are the primary unresolved items.
|
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# Component Type Mapping — Composer Task Types
|
|
2
|
+
|
|
3
|
+
Maps business task descriptions to the 9 closed Composer task types used in SDD authoring.
|
|
4
|
+
|
|
5
|
+
## The 9 Closed Task Types
|
|
6
|
+
|
|
7
|
+
| Task Type | When to Use |
|
|
8
|
+
|---|---|
|
|
9
|
+
| `process` | A human-driven task in a Maestro App queue (the default worklist task) |
|
|
10
|
+
| `action` | An automated in-case action (state transition, data transform, notification) |
|
|
11
|
+
| `agent` | An AI-agent step that reasons or decides (Autopilot agent call) |
|
|
12
|
+
| `api-workflow` | A call to an Integration Service workflow or external REST API |
|
|
13
|
+
| `rpa` | A UiPath Robot-executed workflow (attended or unattended RPA) |
|
|
14
|
+
| `wait-for-timer` | A time-based pause (SLA countdown, scheduled evaluation) |
|
|
15
|
+
| `wait-for-connector` | A pause waiting for an external event via Integration Service connector |
|
|
16
|
+
| `execute-connector-activity` | A direct Integration Service connector activity (sync call, not a workflow) |
|
|
17
|
+
| `case-management` | A nested Maestro case (sub-case spawning or join) |
|
|
18
|
+
|
|
19
|
+
## Mapping Notes
|
|
20
|
+
|
|
21
|
+
- `external-agent` is **not a valid type** in the SDD dialect — it does not exist in Composer. Map it to `api-workflow` (for an Integration Service or REST call) or the appropriate connector type.
|
|
22
|
+
- A task that involves both a human decision and an automated action is typically two tasks: a `process` task followed by an `action` task.
|
|
23
|
+
- UiPath Document Understanding steps are `rpa` tasks (they execute a Robot workflow).
|
|
24
|
+
- Action Center items that do not involve Maestro are outside scope; Maestro cases use `process` tasks for human work.
|
|
25
|
+
|
|
26
|
+
## Decision Tree
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
Is the task performed by a human in a Maestro App?
|
|
30
|
+
→ process
|
|
31
|
+
|
|
32
|
+
Is the task a time-based wait (SLA, countdown)?
|
|
33
|
+
→ wait-for-timer
|
|
34
|
+
|
|
35
|
+
Is the task waiting for an external event (webhook, connector trigger)?
|
|
36
|
+
→ wait-for-connector
|
|
37
|
+
|
|
38
|
+
Is the task calling a UiPath Robot / UiPath workflow?
|
|
39
|
+
→ rpa
|
|
40
|
+
|
|
41
|
+
Is the task calling Integration Service or REST API?
|
|
42
|
+
→ api-workflow (if workflow) | execute-connector-activity (if direct activity)
|
|
43
|
+
|
|
44
|
+
Is the task an AI reasoning/decision step?
|
|
45
|
+
→ agent
|
|
46
|
+
|
|
47
|
+
Is the task spawning or joining a nested Maestro case?
|
|
48
|
+
→ case-management
|
|
49
|
+
|
|
50
|
+
Is the task an automated state change, transform, or notification within the case?
|
|
51
|
+
→ action
|
|
52
|
+
```
|
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
# Maestro Case Management — Schema Vocabulary
|
|
2
|
+
|
|
3
|
+
Vocabulary for case variable types, binding forms, and structural elements in SDD authoring.
|
|
4
|
+
|
|
5
|
+
**Fence:** This document contains vocabulary only. It does NOT contain JSON schemas, Case Designer import formats, or any `case_design_plan.json` / `review_items.json` structure. Those are Composer-internal; this skill never reads or writes them.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## Case Variable Schema
|
|
10
|
+
|
|
11
|
+
Each case variable in §1.5 of the SDD carries:
|
|
12
|
+
|
|
13
|
+
| Field | Description |
|
|
14
|
+
|---|---|
|
|
15
|
+
| Variable | The variable name (camelCase; use inline backticks in SDD) |
|
|
16
|
+
| Category | Input / Output / Intermediate / System |
|
|
17
|
+
| Type | Text / Number / Boolean / Date / Collection / File |
|
|
18
|
+
| Binding | The binding expression (inline backticks) or `—` if unresolved |
|
|
19
|
+
|
|
20
|
+
Category and Type are from closed sets. Do not introduce new categories or types.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## Binding Expression Forms
|
|
25
|
+
|
|
26
|
+
| Form | Syntax (in SDD) | Example |
|
|
27
|
+
|---|---|---|
|
|
28
|
+
| Case-level variable | `` `case.<variableName>` `` | `` `case.loanAmount` `` |
|
|
29
|
+
| Stage output | `` `stage.<stageName>.<variableName>` `` | `` `stage.Review.approvalDecision` `` |
|
|
30
|
+
| Task output | `` `task.<taskName>.<outputField>` `` | `` `task.ExtractLoanData.extractedAmount` `` |
|
|
31
|
+
| Connector field | `` `connector.<activityName>.<field>` `` | — (render as `—` if activityTypeId not provisioned) |
|
|
32
|
+
| Literal | `` `"<value>"` `` | `` `"APPROVED"` `` |
|
|
33
|
+
|
|
34
|
+
When a binding cannot be resolved (no provisioned connection ID or activity type ID), render the cell as `—`. Never fabricate a platform-specific identifier.
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
## System Variables (always present)
|
|
39
|
+
|
|
40
|
+
These variables are automatically available in every Maestro case without explicit declaration:
|
|
41
|
+
|
|
42
|
+
| Variable | Type | Description |
|
|
43
|
+
|---|---|---|
|
|
44
|
+
| `case.id` | Text | Unique case instance identifier |
|
|
45
|
+
| `case.status` | Text | Current lifecycle status |
|
|
46
|
+
| `case.currentStage` | Text | Current stage name |
|
|
47
|
+
| `case.createdAt` | Date | Case submission timestamp |
|
|
48
|
+
| `case.lastModifiedAt` | Date | Last update timestamp |
|
|
49
|
+
|
|
50
|
+
These do not need to be listed in §1.5 unless they are explicitly read or written by a task.
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
## I/O Field Schema (per-task)
|
|
55
|
+
|
|
56
|
+
Each task's I/O table in §2 carries:
|
|
57
|
+
|
|
58
|
+
| Field | Type | Binding |
|
|
59
|
+
|---|---|---|
|
|
60
|
+
| {fieldName} | Text/Number/Boolean/Date/Collection/File | `` `<binding>` `` or `—` |
|
|
61
|
+
|
|
62
|
+
The "Field" column uses the business name (human-readable); the "Binding" column uses the technical binding expression in inline backticks.
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# UiPath Maestro — Case Framework
|
|
2
|
+
|
|
3
|
+
Concepts and patterns for designing Maestro case frameworks used in SDD authoring.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Case Lifecycle
|
|
8
|
+
|
|
9
|
+
A Maestro case moves through these lifecycle states:
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
Submitted → In Progress → [stage transitions] → Completed | Cancelled | Escalated
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
Each stage transition is driven by completion conditions, exit conditions, or SLA breaches.
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Stage Design Patterns
|
|
20
|
+
|
|
21
|
+
### Linear pipeline
|
|
22
|
+
Stages execute in sequence. Each stage starts when the previous completes normally.
|
|
23
|
+
|
|
24
|
+
### Parallel stages
|
|
25
|
+
Two or more stages execute concurrently; a join stage waits for all to complete.
|
|
26
|
+
|
|
27
|
+
### Conditional routing
|
|
28
|
+
A completion/exit condition routes to different downstream stages based on case variable values.
|
|
29
|
+
|
|
30
|
+
### Loop / retry
|
|
31
|
+
A stage can return to an earlier stage on a specific exit condition (e.g. "Return to Review" on rejection).
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## Task Assignment Patterns
|
|
36
|
+
|
|
37
|
+
| Pattern | Task Type | How assignment works |
|
|
38
|
+
|---|---|---|
|
|
39
|
+
| Personal queue | `process` | Assigned to a specific user by case variable or round-robin |
|
|
40
|
+
| Shared queue | `process` | Any qualified user in the queue can claim the task |
|
|
41
|
+
| Role-based | `process` | Assignment rule filters by persona / role attribute |
|
|
42
|
+
| Automated | `action`, `rpa`, `agent`, `api-workflow`, etc. | No human assignment; runs automatically on stage entry or trigger |
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## SLA Patterns
|
|
47
|
+
|
|
48
|
+
SLAs in Maestro operate at stage or task level:
|
|
49
|
+
|
|
50
|
+
- **Business-day SLA** — measured in working hours/days (respects the organization calendar).
|
|
51
|
+
- **Calendar-day SLA** — measured in clock time.
|
|
52
|
+
- **Escalation action** — on SLA breach: reassign, notify, or transition to an escalation stage.
|
|
53
|
+
|
|
54
|
+
SLA values in the SDD are expressed in human-readable form (e.g. "2 business days") and are not bound to a platform-specific format.
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## Variable Flow Patterns
|
|
59
|
+
|
|
60
|
+
Variables flow through the case in four categories (Input, Output, Intermediate, System). Design patterns:
|
|
61
|
+
|
|
62
|
+
- **Pass-through** — an Input variable flows unchanged to an Output (e.g. applicant name).
|
|
63
|
+
- **Transform** — an Intermediate variable is computed from Inputs (e.g. risk score from form fields).
|
|
64
|
+
- **Accumulate** — a Collection variable is built up across tasks (e.g. list of reviewer comments).
|
|
65
|
+
- **Decision** — a Boolean or Text variable records a human or automated decision.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# UiPath Maestro — Case Management
|
|
2
|
+
|
|
3
|
+
Domain knowledge for authoring the SDD's case management sections. Covers Maestro's model, key concepts, and the elements that appear in an SDD.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## What Maestro Does
|
|
8
|
+
|
|
9
|
+
UiPath Maestro orchestrates multi-stage, multi-participant business cases. A **case** is an instance of a **case definition** — a configured process template with stages, tasks, routing rules, and Maestro App views. Cases are persisted, auditable, and can span days or weeks.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Key Concepts
|
|
14
|
+
|
|
15
|
+
| Concept | Description |
|
|
16
|
+
|---|---|
|
|
17
|
+
| Case definition | The configured template (stages, tasks, variables, rules, App views) |
|
|
18
|
+
| Case instance | A runtime execution of the case definition (one per submitted request) |
|
|
19
|
+
| Stage | A logical phase of the case (e.g. "Initial Review", "Approval") |
|
|
20
|
+
| Task | A unit of work within a stage (human or automated) |
|
|
21
|
+
| Queue | A Maestro App inbox where `process` tasks are assigned to users |
|
|
22
|
+
| App view | The Maestro App screen a persona sees when working a `process` task |
|
|
23
|
+
| Case variable | Data that flows through the case (Input/Output/Intermediate/System) |
|
|
24
|
+
| SLA | A time constraint on a stage or task |
|
|
25
|
+
| Entry condition | The condition that must be true for a stage to start |
|
|
26
|
+
| Completion condition | The condition that marks a task or stage as done |
|
|
27
|
+
| Exit / Exception | A condition that routes the case out of the normal path |
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## What Goes in the SDD
|
|
32
|
+
|
|
33
|
+
An SDD documents the case design in Composer's format so that a Maestro admin can configure the case definition. The SDD does NOT replace the Composer Case Designer — it is the design artifact that precedes it.
|
|
34
|
+
|
|
35
|
+
Elements the SDD must capture:
|
|
36
|
+
|
|
37
|
+
- **§1 Case Definition** — trigger, stage sequence, business rules, case variables with categories/types/bindings
|
|
38
|
+
- **§2 Stages & Tasks** — per-stage: entry/completion/exit/SLA + per-task: type, I/O fields with bindings
|
|
39
|
+
- **§3 Personas & App Views** — who works each `process` task and what they see in the Maestro App
|
|
40
|
+
- **§4 Integrations & Triggers** — integration service connections, trigger events, connection IDs (or `—`)
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## SDD Authoring Guardrails
|
|
45
|
+
|
|
46
|
+
- Task types are from the 9-item closed set (see `component-type-mapping.md`).
|
|
47
|
+
- Connection IDs, activity type IDs, action app IDs: render as `—` if not provisioned.
|
|
48
|
+
- No `case_design_plan.json`, `review_items.json`, or `validate-sdd` output — Composer-internal only.
|
|
49
|
+
- Appendix A (readiness) is self-computed; no external data import.
|