Integrated Fields

The integration of Microsoft Dynamics Client and Jobs to Framework ECM is fully customisable via the integration mapping database.

Dbo.FramProj

Dbo.FramProjContact

Dbo.FramProjVariation

Dbo.FwLUPrdHElev

Dbo.FwLUPrdHFacade

Dbo.FwLUPrdHSeries

Dbo.FwLUPrdHType

Dbo.FwLUPrdProm

Dbo.FwLUPrdSType

Dbo.FwLURDiv

Database Models

The following database model(s) displays the manner in which data is integrated between the third party application and Framework Integration.

Integration Process

The following information is a low level account of the integration process including criteria, decisions, and outcomes. This information is technical in nature and is provided "as-is" for a detailed analysis of the integration process for system administrators.

1. Get Default Framework Database Identifier from Preference #-1024
2. Integrate Jobs
1. Get all Framework Jobs from v_fwInt_dnmxJobs where
   1. If IncludeMaintenance is False
   2. job.l_wfl_stgMajor_id <> -5 (Maintenance)
   3. job.l_wfl_stgMinor_id <> -18 (Maintenance)
   4. If OrderCriteria is 1 (all jobs)
   5. Job.l_job_id <> 0 • Job.s_link_accts <> ‘N/A’ Else OrderCriteria is 2 (Single Job)
   6. Job.s_job_num = ‘OrderCriteriaID’
   7. Job.s_link_accts <> ‘N/A’
2. We search for a match in Dynamics framProj table where
   1. framProj.jobPkid = job.l_job_id
   2. framProj.sourceDatabase = value for Framework Db Identifier
3. Known issues that prevent a job from being inserted are
   1. that the Client name is null
   2. Jobs that don’t insert into the db could be in maintenance.
3. Integrate Contacts
   1. Get all Framework Contacts from v_fwInt_dnmxContacts where
      1. Entity.l_entity_id <> 0
      2. Cont.d_pay_iDeposit_act is not null
      3. Job.s_link_accts <> ‘N/A’
      4. Job.l_wfl_stgMajor_id <> -5 (Maintenance)
      5. Job.l_wfl_stgMinor_id <> -18 (Maintenance)
   2. We search for a match in Dynamics FramProjContact table where
      1. FramProjContact.entityPkid = entity.l_entity_id
      2. FramProjContact.projID = job.s_job_num
      3. FramProjContact.sourceDatabase = value for Framework Db Identifier
   3. Known issues that prevent a contact from being inserted are
      1. that the contact name is null
4. Integrate Variations
   1. Get all Framework Variations from v_fwInt_dnmxVarDocs where
      1. Doc.l_doc_id <> 0
      2. Cont.d_pay_iDeposit_act is not null
      3. Job.s_link_accts <> ‘N/A’
      4. Job.l_wfl_stgMajor_id <> -5 (Maintenance)
      5. Job.l_wfl_stgMinor_id <> -18 (Maintenance)
   2. We search for a match in Dynamics FramProjVariation table where
      1. FramProjVariation.docPkid = doc.l_doc_id
      2. FramProjVariation.sourceDatabase = value for Framework Db Identifier
   3. Known issues that prevent a variation from being inserted are
      1. The date field must be between 1/1/1753 and 31/12/9999
5. Integrate other LookUp tables
   1. Framework Prd_sType updates fwLuPrdSType
   2. Framework Prd_hElev updates fwLUPrdHElev
   3. Framework Prd_hFacade updates fwLuPrdHFacade
   4. Framework Prd_hSeries updates fwLuPrdHSeries
   5. Framework Prd_hType updates fwLuPrdHType
   6. Framework prd_prom updates fwLuPrdProm
   7. Framework rDiv updates fwLuRDiv
   8. Where each table pkid matches and the sourceDatabase matches the Framework Db Identifier

When doing the integration, the program looks at job.l_rpt_index2 it gets the number entered in that field and it checks the ini profile for the key OfficeContext(x)=y where x is equal to the value in job.l_rpt_index2. If it finds this key then it puts the value of y into the contextID. If it does not find an officeContext setting for that value then it uses job.l_context_id and copies this value into the contextID fields. So if you change a jobs context identification, it will only change the contextID field if the ini profile has a key for that OfficeContext.

Here's an example Job #1 has a job.l_context_id of 1, but a job.l_rpt_index2 of 270 () If the ini profile has the key OfficeContext(270)=4 then when integration runs, it will set the FramProj.contextID for Job #1 to be 4. If it does not have the OfficeContext key then the FramProj.contextID will be set to the job.l_context_id value of 1. If you then change the context identifier for Job #1 to be (269) then rerun integration, if there is a key called OfficeContext(269)=2 then the FramProj.contextID will change to 2. If the OfficeContext key does not exist then the FramProj.contextId will change to 1. This is because the key couldn't be found so it uses the value in the job.l_context_id field instead.