Skip to content

Executions info panel tweaks#776

Draft
canptura wants to merge 44 commits into
mainfrom
executions_info-panel-tweaks
Draft

Executions info panel tweaks#776
canptura wants to merge 44 commits into
mainfrom
executions_info-panel-tweaks

Conversation

@canptura

@canptura canptura commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

This branch started as little tweaks for the instance info panel but evolved to a whole revamp of the panel and most of it's components.

Details

  • Tab layout and design adapted to reference that was given
    • refactoring of component names for consistency
    • Current Tabs with data: Overview, Details, Data (Milestones & Activity still to do)
  • some style sheets added
  • some components outsourced for code readability

canptura and others added 30 commits May 15, 2026 17:27
@CLAassistant

CLAassistant commented Jun 25, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@jjoderis jjoderis left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice UI.

One thing I'm not sure about is the fact that we show no information at all when no instance is selected. Some of the data exists outside the instance like the "Process/Step image", "Planned" Budget, some of the information in "Details" and the existing Variables shown in "Data". So it might make sense to show that data even when no instance is selected.

Comment on lines +32 to +34
const activityEntries: ReactNode[][] = [];

const activityLog: [string, 'INFO' | 'WARN', string][] = [

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think as of now there is no indication in the logs of an instance that links a log output to a specific activity so this might be a bit harder to do with actual instance data.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think activity is just supposed to be the frontend name for the log display

}
}

export async function getProcessVersion(processDefinitionsId?: string, versionId?: string) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are the parameters optional?

}

export async function getProcessVersion(processDefinitionsId?: string, versionId?: string) {
return processDefinitionsId && versionId

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a permissions check and optimally error handling similar to the other functions.

Comment on lines +27 to +29
status = instance.instanceState.reduce((overallState, state) => {
return ['ENDED', 'STOPPED'].includes(overallState) ? state : overallState;
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not completely sure if I understand what this is doing. If you are checking if the instance is still running you could use the "isActive" function. There is also a "executionStatus" value on the extended instance info returned by the server that indicates if an instance is "Running", "Ended" or "Failed".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously only the state of the first token was returned which resulted in situations were the instance was declared "ended" even though other tokens were still active. That's why I wanted to display the proper status texts but give priority to status other than "ended" and "stopped". (or maybe "aborted" which I yould have added).

It still picks the first one that is not one of the list (or one of the list if nothing else exists) so it ist still not that elaborate or expressive, but I wasen given any other hierarchy or ordering. Do you have an idea which status to display when multiple tokens are/were running?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants