| Subject: | Redesign Integration module in Web framework to improve traceability and simplify workflow |
| Summary: | Integration module in Web framework. Design an integration process that can easily be used to integrate with other systems using a standard set of integration functions. The integration framework should be able to utilize SQL based integration, File output, and API calls. 1. DESIGN Requirements: This design should allow subsidiary modules to compute required integration entries and submit these entries to a standard integration framework. - Integration Setup menu
- This menu controls what modules are integrated and which method is used.
- Integration-specific rules are maintained in this menu
- The following modules should be integrated:
- General Ledger Journals
- Accounts Payable Invoice
- Accounts Receivable Sales Order
- Accounts Receivable Adjustments
- Accounts Receivable Receipts
- System process "SYS009 - Perform all integration tasks." is used to perform all SQL based integration. A SQL API pack needs to be applied to the FMIS database.
- "EnableIntegrationScheduler" configuration in web.config is used to perform File output and API call based integration.
- Data will be entered into the tables associated with 1.2 above then the processes 1.3 and 1.4 will integrate these to FMIS system.
|
| Audit Notes: | |
| 05 Feb 2018 | 04:59PM Comment 1 by Alvis (Link Technologies) Case 9097 added to project 8.3 |
| 06 Feb 2018 | 08:40AM Comment 2 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 06-02-2018 08:40 AM Time Taken: 40.00 |
| The following has been completed: - Integration Setup
- Setup for maintaining available modules and method of integration.
- These entries are pre-defined.
- Each method has its own set of rules which can be changed by the user
- GL Journal, AP Invoice, AR Sales Order, AR Adjustment, and AR Receipt views
- List of all entries showing status, notes, and attachments. File Output API will create the output file in the attachments.
- Users have the ability to edit invalid and resubmit entries.
- System process "SYS009 - Perform all integration tasks." is used to perform all SQL based integration. A SQL API pack needs to be applied to the FMIS database
- "EnableIntegrationScheduler" configuration in web.config is used to perform File output and API call based integration.
|
|
| 16 Feb 2018 | 03:50PM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 16-02-2018 03:50 PM |
| Please proceed with UAT. |
|
| 23 Feb 2018 | 04:17PM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 26-02-2018 12:00 AM Time Taken: 3.00 |
| QA Results Step 1 - Developer will perform test based on test cases provided Step 2 - Product expert to complete Product QA based on test cases.
Test cases are provided on the case header before the case is approved for development. Test Results Summary Table 1 - Summarised list of issues | No | Test Description | Pass/Fail | 1 | Enable the "Integration" for the admin user, and user should be able to access the menu | Pass | 2 | Configure the integration setup for each module. There should be no errors saving configurations | Pass | 3 | Mark the integration modules as "Active". This should be saved without errors. Tested this for all modules under Integration Setup
| Pass | 4 | Schedule the "SYS009" to run every 5 second. This should execute without errors.
| Pass
| 5 | "EnableIntegrationScheduler" is enabled in the web cofig by default | Pass | | 6 | Activate, GLJournalFile and the csv file should be attached in the attachments under GlJournalView. Tested with NFA integration. Case 9131 | Pass | | 7 | Notes is successfully updated to show validations | Pass | | 8 | We were able to edit the posting date and process invalid transaction | Pass |
QA Environment Details - OS version: Windows 7
- Application version:9.2.4
- Database (Demo/New/Client): Demo - LINKSOFTHQ on QA1 and JIWA701 on QA1
Steps to reproduce failed scenarios: Notes : - API Call will be ATO single touch and any other web service API that will be implemented in future Case added to development
|
|
| 25 Feb 2018 | 04:15PM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 25-02-2018 04:15 PM Time Taken: 2.00 |
| Hi Sanjay, This case has been tested as per Comment 4. Case has also been documented Documentation completed under - Point of Sale - WEB - Integration
- Point of Sale - WEB - Integration Setting
- Point of Sale - WEB - Integration -->Integration Setup
- Point of Sale - WEB - Integration--> Setting in FMIS
- Point of Sale - WEB - Integration--> GLJournalView
- Point of Sale - WEB - Integration--> APInvoiceView
- Point of Sale - WEB - Integration--> ARSalesOrderView
- Point of Sale - WEB - Integration--> ARAdjustmentView
- Point of Sale - WEB - Integration--> ARReceiptlView
Please review and close case. Regards
Rashna |
|
| 26 Feb 2018 | 08:18AM Comment 6 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 26-02-2018 08:18 AM |
| Thanks Rashna. |
|
| 09 Oct 2019 | 08:14AM Comment 7 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |