Closed SanaSalem01 closed 1 month ago
@SanaCofinityX please update the ticket - this is a change proposal and not a bug (as it intends when reading the title" please use something like "API Create company account | adding "applicationID" in the response body" this makes it more open. Please also share the info if you want to contribute the code for it.
@jjeroch Ticket summary has been updated.
@jjeroch | @evegufy I would like to ask from which release branch I should checkout for this change! I am assuming it would be https://github.com/eclipse-tractusx/portal-backend/tree/release/v2.1.0-RC1 but please let me know if there is any other release to checkout.
Thanks
@jjeroch | @evegufy I would like to ask from which release branch I should checkout for this change! I am assuming it would be https://github.com/eclipse-tractusx/portal-backend/tree/release/v2.1.0-RC1 but please let me know if there is any other release to checkout.
Thanks
Hi @tfjanjua sure, please check out from main, the open release branch is closed for improvement and features
This api is creating the CompanyInvitation and it make sense to return the Id of CompanyInvitation only. Because the whole process of creating this invitation is in background process so even if we move the application creation in api itself then one have to still wait for the completion of whole process. So idea would be to use this invitation id to fetch the Company application Id and Company Id from a different new api (with same set of permissions as Invitation api have). So far there are two use cases for this
UPDATE: As Because of the issue #700 . Company and application creation is moved in api execution itself so now we no longer need an api to retrieve these ids. So I have updated the @Phil91 PR #960 with this change where Invite api will now return these ids .
@dhiren-singh-007 i assume this solves the ticket ?
@dhiren-singh-007 i assume this solves the ticket ?
Yes @MaximilianHauer , PR #960 will solve this once merged.
Change proposal: Add Company Id,application id in response of ExecuteInvitation api i.e POST: api/administration/invitation
Reason: In automation and CRM communication there was no reference id to track the Invitation.
Current Impact/limitations:
Change proposal impact: So now any system can use Application id and Company Id for reference after invitation.