Skip to content

Executions info panel tweaks#776

Merged
jjoderis merged 60 commits into
mainfrom
executions_info-panel-tweaks
Jun 30, 2026
Merged

Executions info panel tweaks#776
jjoderis merged 60 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 thread src/management-system-v2/lib/data/processes.tsx Outdated
Comment thread src/management-system-v2/lib/data/processes.tsx Outdated
Comment on lines +193 to +194
<EntryKeyText key="instance-name-key">Name</EntryKeyText>,
<EntryValueText key="instance-name-value">{definitionsInfos?.name}</EntryValueText>,

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 thought that you could have new component return the rows you currently create after the fact in your "DataGrid" component directly so you can decide in that function if you need two or one column.

So something along these lines:

const EntryComponent: React.FC<...> = (...) => {
...

if (isHeader) {
  return (
    <Row ...>
      <Col ...>
        ...
      </Col>
    </Row>
  )
}

return (
  <Row ...>
    <Col ...>
      ...
    </Col>
    <Col ...>
      ...
    </Col>
  </Row>
)
}

Comment on lines +505 to +515
) : performers ? (
!!performers?.length && (
<Space>
{performers.map((e) =>
!e.isGuest ? (
<Tag color={'purple'} key={e.id + 'assigned'}>
{e.firstName + ' ' + e.lastName}
</Tag>
) : undefined,
)}
</Space>

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.

Since you are getting this information from the bpmn anyway now you could maybe skip the "logInfo" case above and always show this information.

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.

If I understood correctly there wont be any entries for events that happened yet. So in that case the only way is to fetch the userdata from their IDs given in the bpmn.

@canptura canptura marked this pull request as ready for review June 29, 2026 16:28
@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown

CLOUDRUN ACTIONS

✅ Successfully created Preview Deployment.

https://pr-776---ms-server-staging-c4f6qdpj7q-ew.a.run.app

@jjoderis jjoderis merged commit b0bf9eb into main Jun 30, 2026
12 checks passed
@jjoderis jjoderis deleted the executions_info-panel-tweaks branch June 30, 2026 14:08
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