Update TaaS Intake Form: Backend Calls - Goal Due Date: 12/5

[acshields]

• Required Skills and Preferred Skills reference data needs updating to use EMSI standard.
• Once TaaS intake form is submitted, the "Bookings API" (name TBD) should be called and a record for each requested role, along with the associated skills, should be created.

Tasks here (this list is managed by @maxceem)

• create jobs on TaaS project creation
• update skill dropdowns to list skills from Skills API
• skills dropdowns should load all the pages from Skills API (and don't' make duplicate calls for each skills dropdown instance)
• show TaaS Project link after project creation

[acshields]

@RishiRajSahu - This is the issue I gave you a heads up on a couple weeks ago, regarding some future updates that will be needed for the TaaS intake form. As you prepare for this feature, I would recommend chatting with Will Price and Nagendra (he will be owning TaaS App from the engineering standpoint) to learn more about the "Bookings API" they are currently planning, as well as any other questions you might have.

[wdprice]

The APIs are still in development, but I can at least outline the top level items.

• Skills selection list must populate with values pulled from api.topcoder.com/v5/skills. A skill provider id will need to specified - we will provide this at the time of implementation

• Create project as you do today on v5/projects, with a Type= TaaS. (I'm sure the actual field is different, we can hammer that out.

• POST the job, job description, number of openings, list of required skills, and other relevant values to to v5/jobs (swagger here)

• Update the the link on the button the appears on conclusion of intake to direct the user to TaaS-App (URL structure TBD)

[wdprice]

@RishiRajSahu @acshields - FYI, our TAAS APIs should be deployed to topcoder-dev tomorrow. Once deployed this ticket should be able to be worked on.

cc: @nkumar-topcoder

[nkumar-topcoder]

@RishiRajSahu @acshields Dev deployment of taasapp completed.
The Dev integration For taasapp is completed. You can verify for JOB creation. Few pointers.

1. Endpoint : http://api.topcoder-dev.com/v5/taasapi/jobs
2. Swagger & Postman collection : https://github.com/topcoder-platform/taas-apis/tree/dev/docs
3. Roles: bookingmanager and u-bahn (pshah_manager user already has this. for other user testing, that user needs to be part of v5/users). For job creation booking manager roles is mandatory.

cc: @wdprice

[RishiRajSahu]

Thanks @nkumar-topcoder for the info, will let you know about queries if arises

[RishiRajSahu]

@wdprice @nkumar-topcoder
I been through the swagger as well as requirements mentioned by @acshields and support provided by your backend apis - So these are the things required -

1. Updated skills api endpoint, currently we are using v3 it needs to be replaced with V5
2. The job object is mapping to each kind of resource option we provide in the form i.e. QA, Frontend, Backend etc. so a respective job(s) should be created for each type of resource when the project is created
3. On Project creation success page, provide the url to TaaS app for TaaS projects only

Now below are my updates for each of above requirements
1. Could you provide me the swagger for V5 skills ?
2. This would need the Connect backend api(which is projects api) to be updated so as and when the TaaS project creation is done we make call to TaaS backend also to create job(s), I personally not in favour of having any TaaS app/api logic reside on Connect Frontend/Backend side, it will unnecessarily create dependency/maintenance overhead. What my suggestion is to create a separate processor which listens to project's creation event(like how salesforce is doing) and take the event's payload and do all the processing required for TaaS app/api, maybe we can name that processor - TaaS-Processor,
Pros -

• All logic for TaaS resides in the processor, good scenario to exploit our event bus
• Deployment/change dependency removed from Connect
• Extensible - in processor we can in future listen for other api's events also if required

Cons-
Effort to create new processor, which seems worth doable to me. I would be happy to take ownership of that if required as I am very well aware of what payload we send on the event and what your api's need as per swagger

3. Let us know the URL we can do it as and when required.

FYI @mtwomey @vikasrohit

[nkumar-topcoder]

@RishiRajSahu

1. V5/User, v5/skills etc
   —————
   Swagger: https://github.com/topcoder-platform/u-bahn-api/blob/master/docs/swagger.yaml
   Example:
   http://api.topcoder-dev.com/v5/users?handle=
   http://api.topcoder-dev.com/v5/skill-search/skills?organizationId=0d2320f9-be61-4ba4-973e-edc3bb682a69&keyword=selenium
2. Very well thought out analysis, can we have call with other stakeholder to discuss and finalize.
   @wdprice please share you thoughts, further we can take this offline.
3. This part is WIP, tentative :https://mfe.topcoder-dev.com/taas/myteams will confirm shortly.

[nkumar-topcoder]

@RishiRajSahu
Regarding 2nd point for separate processor for Job creation, my view is
a) we are creating intake app for taas-app.
b) And, once intake form is complete - posting taas end point
both are specific to taas requirement. Hence, only for posting to taas endpoint having a separate processor i believe is overhead in terms of publishing and consuming.

I understand your point on dependency but there is already intake app which is specific to project.
your thoughts please

[RishiRajSahu]

@nkumar-topcoder If intake for TaaS is always going to be via new taas-app once released ? or Connect will also keep providing the option to create a TaaS intake ? If we are completely getting away from Connect for TaaS intakes then yes we don't need another processor and all the logic could reside in new taas-app.

[nkumar-topcoder]

@RishiRajSahu need to check from business view
cc : @wdprice

[nkumar-topcoder]

@RishiRajSahu
Post discussion it has been decided to post for job from intake form.
thanks @vikasrohit @wdprice

[RishiRajSahu]

@nkumar-topcoder I think in this scenario it would be best to consume the event once the project is created, could you guys give heads-up on this so that I can launch the challenge for taas-processor ?

fyi @mtwomey