14691 COLIN states mapping to LEAR RFC

[argush3]

Issue #: #14691

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

[severinbeauvais]

My first thought was that the new way appears more complicated than the COLIN way. However, I really like the idea of managing "allowable transitions". When implemented, the new approach is likely to be easier to use.

[thorwolpert]

we should kick this around a bit more.
rc chat threads aren't going to get us there, even though this is really close.
thanks for gathering this.

[severinbeauvais]

Are we still pursuing the concept of sub-state?

[argush3]

Are we still pursuing the concept of sub-state?

I don't think so.

We will have things like good standing, warnings(compliance, missing business info) and other flow statuses to give us what we need.

[severinbeauvais]

Are we still pursuing the concept of sub-state?

I don't think so.

We will have things like good standing, warnings(compliance, missing business info) and other flow statuses to give us what we need.

How will we know things like Frozen, or in various dissolution states?

[severinbeauvais]

Looks workbable to me 👍

[argush3]

@severinbeauvais A note about the frozen flag. There is already an adminFreeze flag passed back by the BE on the business object. This can be used.

[severinbeauvais]

@severinbeauvais A note about the frozen flag. There is already an adminFreeze flag passed back by the BE on the business object. This can be used.

Thanks. Travis is looking into this as well (so Auth Web knows). FYI.

[thorwolpert]

We seem pretty close and narrowing in on smaller details.
Do we want to fully work it out, or if we're pretty close get it in to start trying it?

[severinbeauvais]

If we're worried about the volume of data, we could move this part of the response to an actions sub-endpoint, or allow for a ?verbose=minimum flag to allow the caller to reduce.

In a business response object, I think a "large" amount of data is OK.

In a filings response object, I'd prefer to see minimum data returned, and the UI can make another call to fetch more data when the user needs it. But I don't know how this would work for the API telling us "you're allowed to correct this item" (which is business logic currently in the UI). I also don't know how the API will inform the UI whether, say, the business can be dissolved (which is more business logic in the UI)... though this flag/rule could be in the business response object.

[thorwolpert]

As far as I can see, this captures all of our discussions, learnings from the business and pulling the design into a way we can keep valid tests and scenarios in the CI pipeline.
I like it.