Release 1.4.0 (Released on Aug 25, 2020)

• Kafka based event consumers
• Passing through more events without any filter or modification to Salesforce (Allowing Progressive registration to work without dedicated Connect login/reg pages)
• More automation flows for Salesforce events

Salesforce Lead/Opportunity status sync

Now few lead and opportunity events are listened in the app and project's status is changed accordingly as mentioned in the following issue #52

Added budget and deadline fields

Four new fields are added to be synced to the lead.

TC_Connect_Budget__c
TC_Connect_Budget_Type__c
TC_Connect_Deadline__c
TC_Connect_When_To_Start__c

Added Google Analytics information and Topcoder handle

Added two Google Analytics fields namely, _gclid and _gacid to the salesforce lead when a lead is created from connect project.
Added topcoder handle of the user who created the project in connect lead.

Minor release to sync description field

This release includes changes to sync description field from connect project to salesforce lead.

Phase 2 for Salesforce lead integration (Update supported now)

• Added more connect project information to lead record in SFDC:
  -- Connect project link: https://connect.topcoder.com/projects/[ID]
  -- Connect reference code
  -- Connect project status
• Integrated the update event for connect projects for following fields
  -- refCode
  -- status
  -- cancelReason
• Project Direct Project Id captured in Lead and Opportunity

Configurable schedule for failed messages

Minor release to have

• configurable schedule for scheduler worker which processes the failed messages.
• debugging statements for investigating the missing customer case

Scheduled worker for processing failed messages

• This release includes a scheduled worker to process all failed messages. As of now it fetches messages every minute and process them. This is done to prevent server from getting exhausted from resources because continuously processing (assuming messages are being failed because of a logical bug in the application) failed messages, until a bug in the code is fixed.
• It still does not address the cases where lead is not created in the salesforce because the worker was not able to find a customer role user, even though there exists one, for the project. This is happening occasionally and till date we are not able to reproduce it on local or dev env. For now, leads have to be created manually for such cases.

First release for connect salesforce integration

• Creates a lead in salesforce whenever a project is created by a 'customer' role user in Connect. The lead is created with default status set in salesforce configuration.
  It populates following fields from Connect project data:
  FirstName: <Connect User First Name>
  LastName: <Connect User Last Name>
  Email: <Connect User Email>
  LeadSource: 'Connect' //hardcoded
  Company: 'Unknown' // hardcoded
  OwnerId: <Salesforce user Id who should be owner of the leads _
  TC_Connect_Project_Id__c: <Unique ID of each Connect project>
• Lead is created only when project is created. It is not updated by system afterwards for any of the project lifecycle events. Future releases may support progressing the salesforce lead through its lifecycle as Connect project moves through its own.
• This release moves failed messages, from the original queue, to a separate queue which no one listens right now. This is done to prevent server being exhausted, when a message fails due to a bug in application, unit the bug is fixed. Future release might support some mechanism to consume those failed messages automatically, however, right now it has to be done manually by looking at CloudAMQP admin interface.