Schlumberger
Borsig
Abemac
Kavo https://sanacommerce.visualstudio.com/Sana%20Projects/_workitems/edit/88717/
How to Add remove the required field from JS/ Add remove asterisk (*)
Validation
Project : Kavo935
page.profile.register.js
How to Add remove the required field from JS
// Show Taxno for B2c Customers $(".field-customer-taxno").show(); // Add asterisk sign via Jquery from a label var labelText = $("label[for = Customer_TaxNo]").text(); labelText = labelText + '*' $("label[for = Customer_TaxNo]").text(labelText); // Set TaxNo as Required field. $("#Customer_TaxNo").rules("add", "required")
// Hide Taxno for B2c Customers $(".field-customer-taxno").hide(); // Remove asterisk sign via Jquery from a label var labelText = $("label[for = Customer_TaxNo]").text(); $('label[for = Customer_TaxNo]:contains("*")').text(function (i, txt) { return txt.replace('*', ''); }) // Remove TaxNo as Required field. $("#Customer_TaxNo").rules("remove", "required")
interface creation mail template
Hi Aji,
Please
share the following details with the ERP Partner of TopMedia.
I am Sandun
Kodagoda the Software developer, contacting you on behalf of the
customization team of Sana web shop. According to the customizations at RQS, we need
some interface changes between ERP and the Sana.
Furthermore, you can find
an overview of interface changes and related RQS customizations in a matrix
format below. This would allow you to understand which customizations are
related to which interface changes.
|
Interfaces |
Nature of Customization: New or Existing ERP Function |
3.1 Search – Product Finder |
3.2. Product grouping – Create groups via product in Sana |
|
GetProductType |
New |
X |
|
|
GetProducts |
Existing |
X |
X |
In the attachment
you will find the list of directories, each directory corresponds to an
interface (function) that has to be changed/updated in the ERP to accomplish
requested customizations. Each folder contains:
1.
[original] folder with the samples of the original reques.xml and response.xml
inside.
2.
V1.0 folder with the samples of the reques.xml and response.xml inside, so you
will be able to see all changes in the XML structure.
3.
Version document(Version.docx) where all needed changes are described.
You can use the example requests to test the new
functionality. You may need to modify the data to some extent, like some
Id’s.
After that you will be able to use “Manual Process Requests”
in the ERP to execute request and verify the changes.
Information about “Manual Process Requests” can be found at https://help.sana-commerce.com/sana-commerce-93/erp-user-guide/sap/manual-process-requests
Important Note:
Once you have done the changes and deployed to the test environment,
please make sure to send us working request and response files per operation (i.e.
GetOrders_Request.xml, GetOrders_Response.xml) with valid data combined
in a zip file, to confirm all the required changes have properly been made. If multiple scenario’s apply (e.g. GetOrders in this case), please provide the files from your
tests for those scenario’s.
Example:
We will be setting up a call to clarify the above requested
interface changes and to answer any interface related questions you may have.
You may refer below help links to get an understanding of
how the Sana code units should be modified according to customizations.
https://community.sana-commerce.com/HelpSupport/Documentation/Technicaldocumentation.aspx
business-central:
https://help.sana-commerce.com/sana-commerce-93/erp-user-guide/dynamics-365-business-central/manual-process-requests
Starter Site Transfer Checklist
https://sanacommerce.visualstudio.com/Sana%20Projects/_wiki/wikis/Sana-Projects.wiki/1146/-SL-Starter-Site-Transfer-Checklist
Project
Hatwee
starter site checklist
|
Item No |
Description |
Starter Site/RQS |
Comments |
|
01 |
Sana version ·
Check the Sana version which will be used for
this project |
9.3.5 (Both) |
|
|
02 |
ERP version and add-ons ·
Check the ERP and the ERP version |
Sap b1(Both) |
|
|
|
·
Check the web
service URL o Development
(in Start) o Live if
available |
Webservice URL, Beta web shop: available Starter site: not available Live: not available in both |
|
|
|
·
Check the listed add-ons installed in your
ERP which might impact the web shop (Perfion/ECON/InRiver) |
Beta site: Ingenico,Kbc Paypage
installed. RQS : Ingenico only |
|
|
03 |
Target audience (B2B/B2C/Both) |
B2B |
|
|
04 |
Shop sales
scenario (Open/Closed) |
|
|
|
05 |
Languages ·
Check the
languages installed ·
Will update additionally
installed addons |
RQS: EN, FR, NL Beta: NL-BE, FR-BE |
|
|
06 |
·
·
|
|
|
|
07 |
HTML injection ·
HTML injection available? |
No |
|
|
08 |
SSL certificate ·
SSL certificate for development/beta web service required? (Available
in Start) |
Not available in start |
|
|
09 |
Start details are
up-to-date? |
|
|
|
10 |
VPN availability? ·
For development web service (Available in
Start) ·
For web server access (Available in
Start) |
No VPN |
|
|
11 |
Performance on starter Site ·
Are there any performance
concerns? (Will
be available in Sphere) |
NA |
|
|
12 |
Task Service ·
Task Service available? ·
Check whether the version
match with RQS and front end ·
Check whether the Task
Service can be stopped and start manually |
Yes, Yes Yes |
Task Service available Both are same (9.3.5) Can stop |
|
13 |
Hosting (External/Internal) |
Internal |
|
|
14 |
Payment Service Providers ·
Do they work? ·
Provide available information
if any |
Ingenico, KBC Payment provider (not in RQS). Ingenico: Works KBCP: Details not configured in Beta/Start |
|
|
|
|
|
|
|
15 |
Third party integrations
(Perfion/Econ) ·
Are info available in
Start? (Test/Live) |
No integrations |
|
|
16 |
‘Variants’, ‘BOM’, ‘Related Products/Mix and
Match’ are available ? |
No |
|
|
17 |
Customer specific assortments available? |
No |
|
|
18 |
Known Sana issues (Available
in Sphere) |
|
|
|
19 |
Known ERP
issues (Available in Sphere) |
|
|
D:\Projects\Applications\AirsysBeta\TaskService\Sana.Commerce.TaskService.exe"
right click >properties > details tab
Subscribe to:
Posts (Atom)