Abonnieren

UiPath Automation Hub

Die Anleitung für UiPath Automation Hub

Automatisierungsphase und -status

Automatisierungsideen

Eine Idee, die über einen mitarbeitergesteuerten oder CoE-gesteuerten Pfad freigegeben wird, muss sequenzielle Schritte durchlaufen, damit aus einer Idee eine Automatisierung live in der Produktion wird. Auf diesem Weg können der Programm-Manager, der Einreicher und die Mitarbeitenden sowie die Benutzer, die der Idee folgen, den Status der Idee nachverfolgen und den verschiedenen Stakeholdern melden, damit geeignete Entscheidungen getroffen werden können.

📘

Hinweis:

Die folgenden Benutzer können die Phase und den Status einer Idee wie unten beschrieben aktualisieren:
Systemadministratoren und Programm-Manager können die Phase und den Status jeder Idee aktualisieren.
Der Benutzer, dem die Projektmanager-Rolle in dieser Idee zugewiesen ist, kann sie während der Implementierungsphasen aktualisieren.
Jede benutzerdefinierte Rolle, der die Berechtigung Phase und Status beliebiger Ideen aktualisieren zugewiesen wurde.

Phasen erfordern bestimmte Aktivitäten, um eine robuste und hochwertige Pipeline zu erhalten. Änderungen bei Phasen oder Status werden den entsprechenden Benutzern mitgeteilt, damit sie aktiv werden und sicherstellen können, dass der Lebenszyklus von Ideen voranschreitet.

Phasen

Nachfolgend finden Sie eine Tabelle mit den Phasen, die für eine Automatisierungsidee verfügbar sind, sowie dem Trigger und einer kurzen Beschreibung für jede von ihnen.

Phase NameTrigger TypeDescription
IdeaAutomaticThe details of an idea are saved by the user.
AssessmentAutomaticWhen an automation idea in Idea - Awaiting review is approved.
This phase is completed by the Process Owner who understands the task or process in detail.
An idea is shared through the CoE-driven path by an authorized user.
QualificationAutomaticWhen the Process Owners clicks Submit Assessment in the edit mode of the automation profile the phase is updated to Qualification.
AnalysisManuallyThe Project Manager updates it from the Automation Profile - About page.
Solution DesignManuallyThe Project Manager updates it from the Automation Profile - About page.
DevelopmentManuallyThe Project Manager updates it from the Automation Profile - About page.
TestingManuallyThe Project Manager updates it from the Automation Profile - About page.
LiveManuallyThe Project Manager updates it from the Automation Profile - About page.

Status

Jeder Phase können verschiedene Status zugeordnet werden, um eine verbesserte differenzierte Nachverfolgung zu ermöglichen.

Nachfolgend finden Sie eine Liste der für jede Phase verfügbaren Status und die Beschreibung der Trigger-Aktion.

Ideenphase

StatusTrigger
Awaiting ReviewThe user clicks Share idea in the Review screen of the shared an idea journey. The Automation Profile Page is created at this point.
DuplicateThe Idea Approver clicks Mark as duplicate for an idea. This status marks it as being a duplicate of another idea.
RejectedThe Idea Approver clicks Reject for an idea.
A reason for the rejection needs to be selected. The below options are available:
Inadequate for idea
Requires edits
Contains dummy information
Other
ArchivedUpdated when:
the Idea Approver clicks Reject for an idea and selects the "Contains dummy information" reason.
The Idea Approver clicks Archive for an idea.

📘

Hinweis:

Die obigen Statusaktualisierungen können auch vom Programm-Manager oder einer benutzerdefinierten Rolle durchgeführt werden, der die Berechtigung „Phase und Status beliebiger Ideen aktualisieren“ zugewiesen wurde.

Bewertung

StatusTrigger
Awaiting ReviewAn idea is shared through the CoE-driven idea flow by an authorized user.
Not StartedThis is set when the Idea Approver approves the automation.
In ProgressThe Process Owner clicks Save in the edit mode of the automation profile page.
On HoldThe Program Manager edits the Status to On Hold from the edit mode of the automation profile page - Phase Status dropdown, for an idea in the Assessment phase.
PostponedThe Program Manager edits the Status to Postponed from the edit mode of the automation profile page - Phase Status dropdown, for an idea in the Assessment phase.
RejectedThe Program Manager edits the Status to Rejected from the edit mode of the automation profile page - Phase Status dropdown, for an idea in the Assessment phase.
ArchivedThe Program Manager or System Admin clicks Archive in the the edit mode of the automation profile page. This is applicable for ideas in the Assessment phase - status Awaiting Review, Not started, In progress, On Hold.

Qualifikation

StatusTrigger
Awaiting ReviewThe Process Owner clicks Submit Assessment from the edit mode of the automation profile page
This is applicable if the Submitter did not choose the Major change expected option for any of the first 2 questions from the Detailed information section.
On HoldThe Program Manager or System Admin selects a batch of ideas that are in Qualification with Awaiting review or Approved status and moves them to Qualification with On hold status by clicking Put on hold.
This is applicable to ideas for which the Board decided to revisit at a later date.
This can be easily done in the Decision Pipeline view.
ApprovedThe Program Manager or System Admin selects a batch of ideas that are in Qualification with the Awaiting review or On hold status and moves them to Qualification with Approved status by clicking Approve.
This is applicable to ideas for which the Board decided to move towards implementation.
This can be easily done in the Decision Pipeline view.
RejectedThe Program Manager or System Admin selects a batch of ideas that are in Qualification with Awaiting review, On Hold or Approved status, and moves them to Qualification with the status Rejected by clicking Reject.
This is applicable to ideas for which the Board decided to stop the process.
This can be easily done in the Decision Pipeline view.
ArchivedThe Program Manager or System Admin clicks the Archive button from the edit mode of the automation profile page.
This is applicable for ideas in the Assessment phase - status Awaiting Review, On Hold, Approved, or Rejected.
This can be easily done in the Decision Pipeline view.

Analyse, Lösungsentwurf, Entwicklung, Testen

StatusTrigger
Not StartedManually updated by the Project Manager in order to mark that the automation development is not started.
In ProgressManually updated by the Project Manager in order to mark that the automation development is evolving as expected.
CancelledManually updated by the Project Manager in order to mark that the automation development is canceled.
On HoldManually updated by the Project Manager in order to mark that the automation development is put on hold.
At-RiskManually updated by the Project Manager in order to mark that the automation development time frame may be delayed.
DelayedManually updated by the Project Manager in order to mark that the automation development time frame is delayed.
CompletedManually updated by the Project Manager in order to mark that the automation development is completed.
ArchivedThe Program Manager or System Admin clicks the Archive button from the edit mode of the automation profile page.
This is applicable to ideas in any of the above-mentioned phases, and status.

Live

StatusTrigger
Ready for ProductionManually updated by the Project Manager in order to mark that the automation development is done and it is ready for the last updates before being published.
HypercareManually updated by the Project Manager in order to mark that the functionality of the automation is being monitored before being published.
If some details need attention, troubleshooting and issue fixes are applied.
In ProductionManually updated by the Project Manager in order to mark that the automation is published.
On HoldManually updated by the Project Manager in order to mark that the automation requires additional input or resolution from a third party.
ArchivedThe Program Manager or System Admin clicks the Archive button from the edit mode of the automation profile page.
This is applicable to ideas in any of the above-mentioned phases, and status.

Citizen Developer-Automatisierungen

Die Automatisierung, die von einem Citizen Developer freigegeben wird, muss sequenzielle Schritte von der Einreichung bis zur Einsatzbereitschaft durchlaufen. Auf diesem Weg können der Citizen Developer-Einreicher, die geschäftlichen und technischen Prüfer, Mitarbeitenden sowie die Benutzer, die der Automatisierung folgen, den Status nachverfolgen und den verschiedenen Stakeholdern melden, damit geeignete Entscheidungen getroffen werden können.

Phasen erfordern bestimmte Aktivitäten, um eine robuste und hochwertige Pipeline zu erhalten. Änderungen bei Phasen oder Status werden den entsprechenden Benutzern mitgeteilt, damit sie aktiv werden und sicherstellen können, dass die Automatisierung im Lebenszyklus voranschreitet.

PhaseDescription
Business ReviewThis Phase enables the Business Reviewers to push forward automations created by the Citizen Developer Self User and select which automations are worth being endorsed for a Technical Review.
Technical ReviewThis Phase enables the Technical Reviewers to push forward automations by identifying any code quality issues and seeing it to the Development phase, if the case.
DevelopmentThis Phase enables the Citizen Developer Power User to select which automations they want to work on and complete the development.
LiveThis Phase enables the Technical Reviewers to approve automations for wider use.

Status

Jeder Phase können verschiedene Status zugeordnet werden, um eine verbesserte differenzierte Nachverfolgung zu ermöglichen. Zudem können bestimmte Aktionen nur ausgeführt werden, wenn sich die Automatisierung in einer bestimmten Phase mit einem bestimmten Status befindet, um die Qualität der Automatisierungspipeline sicherzustellen.

Nachfolgend finden Sie eine Liste der für jede Phase verfügbaren Status und die Beschreibung der Trigger-Aktion.

Phase der geschäftlichen Überprüfung

StatusTrigger
Awaiting ReviewThe user clicks Share in the automation submission form. The Automation Profile is created at this point.
On HoldThe Business Reviewer selects the action Put on Hold from the Automation Pipeline table or from the Automation Profile - About page.
RejectedThe Business Reviewer selects the action Reject from the Automation Pipeline table or from the Automation Profile - About page.
ApprovedThe Business Reviewer selects the action Approve from the Automation Pipeline table or from the Automation Profile - About page.
ArchivedThe Business Reviewer selects the Archive button from the edit mode of the automation profile page.

Phase der technischen Überprüfung

StatusTrigger
Awaiting ReviewThe Business Reviewer selects the action Move to Technical Review from the Automation Pipeline table or from the Automation Profile - About page.
On HoldThe Technical Reviewer selects the action Put on Hold from the Automation Pipeline table or from the Automation Profile - About page.
Rework RequiredThe Technical Reviewer selects the action Rework Required from the Automation Pipeline table or from the Automation Profile - About page.
ArchiveThe Technical Reviewer selects the Archive button from the edit mode of the automation profile page.

Entwicklungsphase

StatusTrigger
Not StartedThe Program Manager approves the automation for Citizen Development Power User Work by selecting the action "Approve for Citizen Developer" work from the Automation Pipeline table or from the Automation Profile - About page.
In ProgressThe Citizen Developer Power User selects the action Start Development from the Automation Pipeline table or from the Automation Profile - About page.

Live-Phase

StatusTrigger
In ProductionThe Technical Reviewer selects the action Approve from the Automation Pipeline table or from the Automation Profile - About page.
ArchivedThe Program Manager clicks the Archive button from the Automation Pipeline table or from the Automation Profile - About page.
This is applicable to automations in any of the above-mentioned phases, and status.

Aktualisiert vor 3 Monaten


Automatisierungsphase und -status


Auf API-Referenzseiten sind Änderungsvorschläge beschränkt

Sie können nur Änderungen an dem Textkörperinhalt von Markdown, aber nicht an der API-Spezifikation vorschlagen.