Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CoE Starter Kit - BUG] Prep work for Support of unpublished flows #5791

Closed
20 tasks done
Jenefer-Monroe opened this issue Jun 12, 2023 · 2 comments
Closed
20 tasks done
Assignees
Labels
coe-starter-kit CoE Starter Kit issues enhancement New feature or request

Comments

@Jenefer-Monroe
Copy link
Collaborator

Jenefer-Monroe commented Jun 12, 2023

Does this bug already exist in our backlog?

  • I have checked and confirm this is a new bug.

Describe the issue

Things to note:

  • In the first iteration of this, only the sync flow architecture will return the unpublished flows.
  • EO-June the List Flows as Admin V2 will return the second required GUID so that unpublished flows can be identifiied

Things to do (July release):

  • Data Export : Mark all flows as published (until the work to return unpublished flows is done)
  • Field : Add a field to track this flowIsPublished
  • Basic inventory : for now just mark all flows as published when inventoried
  • Basic inventory : mark all flows as published for now in delete bad data
  • PPAdmin app - Create new views for unpublished flows
  • PPAdmin app - Filter them out of all other views and subgrids
  • PPAdmin app - Update command bar actions to not show manage permission for unpublished flows.
  • PPAdmin app - Update command bar actions to not show delete for unpublished flows.
  • PPAdmin app - Update command bar actions to not show turn on and off for unpublished flows.
  • Flow permissions apps - filter out unpublished flows

Changes for August:

  • DLP Editor (old) - filter out unpublished flows
  • DLP Editor (new) - filter out unpublished flows
  • DLP Editor (flow) - filter out unpublished flows
  • Filter out of Flow Action Details
  • Inactivity flows and apps - filter out unpublished flows
  • compliance flows and apps - filter out unpublished flows
  • orphan processes - filter out unpublished flows
  • PBI - Update all Flow related pages to either filter out unpublished or include state (published/unpublished) in the visuals
  • Look for unpublished and filter them out for now (so that when the feature lights up we are safe)

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.9

What app or flow are you having the issue with?

kit wide

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

@Jenefer-Monroe Jenefer-Monroe added bug Something isn't working coe-starter-kit CoE Starter Kit issues labels Jun 12, 2023
@Jenefer-Monroe Jenefer-Monroe self-assigned this Jun 12, 2023
@Jenefer-Monroe Jenefer-Monroe added enhancement New feature or request and removed bug Something isn't working labels Jun 12, 2023
@Jenefer-Monroe Jenefer-Monroe changed the title [CoE Starter Kit - BUG] Support of unpublished flows [CoE Starter Kit - BUG] Prep work for Support of unpublished flows Jul 19, 2023
@Jenefer-Monroe
Copy link
Collaborator Author

Work in preparate of these being returned is not complete and in testing for August release.
Work once these are returned to actually light them up in the inventory will be covered by #6111

@CoEStarterKitBot
Copy link
Collaborator

@Jenefer-Monroe This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coe-starter-kit CoE Starter Kit issues enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants