Changes for page crm

Last modified by Kyle Hill on 2025/05/27 11:26
<
From version < 2.3 >
edited by Rudi Marais
on 2023/05/22 23:50
To version < 3.8 >
edited by Kyle Hill
on 2025/05/27 10:40
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -xwiki:technical-documentation.analysis.WebHome
1 +technical-documentation.analysis.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rudim
1 +XWiki.kyleh
Content
... ... @@ -1,1 +1,65 @@
1 -* [[.NET 6 Hosting Bundle>>https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.3-windows-hosting-bundle-installer]]
1 +===== **Required .NET Hosting Bundles:** =====
2 +
3 +* [[.NET 6 Hosting Bundle>>https://dotnet.microsoft.com/en-us/download/dotnet/6.0]]
4 +
5 +
6 +===== **Ensure the following .NET Runtimes are installed:** =====
7 +
8 +[[image:image-20250527112257-1.png]]
9 +
10 +
11 +===== **Testing and Debugging:** =====
12 +
13 +* Check the system event viewer for any errors. Framework related and logs appear here if not successfully written to the logs. This may point to folder permission issues.
14 +
15 +===== =====
16 +
17 +===== **Deployment Considerations:** =====
18 +
19 +* IIS project name should be in the name of the domain in reversed:
20 +** Format: ~{~{host_name}}
21 +** Example: za.co.site.uapi
22 +* Each API under the CRM project should have Its own app pool.
23 +** Format: ~{~{host_name}}.~{~{api_name}}.~{~{version}}
24 +** Example: za.co.site.uapi.identity.v1
25 +* Each API under the CRM should be deployed as a virtual application linked to its relative app pool.
26 +* App pool considerations:
27 +** .NET CRL Version: No Managed Code
28 +** Managed Pipeline: Integrated
29 +* Each API project should be in the root directory of the project.
30 +* Under the root directory, there is a wwwroot folder, which should contain a blank folder for each of the API projects.
31 +* Ensure you replace all the connection strings, file paths and branding of the currently client with the new one. 
32 +* Clear out all the logs for each of the API projects and ensure IIS user has required permission to write to this directory
33 +** Directory: "//za.co.site.uapi\EBSphere.Api.v1.Workflow\logs//"
34 +
35 +===== =====
36 +
37 +===== **Database Considerations:** =====
38 +
39 +* Some databases are setup to require a reference number when making structural changes to the database:
40 +** Create a session reference: (% style="color:#2980b9" %)//exec//(%%)// sp_set_session_context 'ReferenceNo', '123456789'//
41 +** The reference number is the ticket number of the project, as found on our Issue log system.
42 +* Depending on the state of the database, there might be tables, procedures, views and even data that need to be added. Is a list of some of some these objects, that need to be present in the database for the CRM to work correctly (//Please feel free to added on//):
43 +
44 +|=Object Type|=Name|=Dependencies
45 +| |api.sp_AddSupplier_Se|
46 +| |api.sp_BankAccountTypes_SelectV2|
47 +| |api.sp_Communication_Add|
48 +| |api.sp_Communication_AddProperty|
49 +| |api.sp_Content_Add|
50 +| |api.sp_Content_AddProperty|
51 +| |api.sp_CreateSupplier|
52 +| |api.sp_CRM_RegisterUser|
53 +| |api.sp_CRM_ResetPassword|
54 +| |api.sp_DocumentCategories_SelectV2|
55 +| |api.sp_Documents_SelectV2|
56 +| |api.sp_GetBBBEE_Levels|
57 +| |api.sp_GetPersonDetailsV2|
58 +| |api.sp_GetSupplierTypes|
59 +| |api.sp_GetUniversalBankBranch|
60 +| |api.sp_MemberBankDetails_SelectV2|
61 +| |api.sp_MemberBeneficiaries_SelectV2|
62 +
63 +
64 +
65 +
image-20250527112257-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kyleh
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content

Applications

Navigation

Need help?

If you need help with XWiki you can contact: