Please make sure customized Customclass can work in V184.108.40.206 version.
Initially I tried with xml entry <Inclusion section="GSM.PackagingSpec.*" handlerRef="Customclass"/> and few of the sections like specsummary, approved usage(which is a custom class implementation) showed readonly, but the supporting documents section was still editable.
Then I specifically changed to <Inclusion section="GSM.PackagingSpec.SupportingDocuments" handlerRef="Customclass"/> , it hits the custom class implements the read only logic but the UI shows as editable.
It needs to modify your logic for SupportingDocuments because Supporting Documents are changed from V220.127.116.11.
As per the SLE extension document provided in the below feature pack
Oracle Agile Product Lifecycle Management for Process
Feature Pack 4.2
AS per the extension document for SectionLevelEditing extension, below is the list of section Id's supported for packaging spec:
AS per my understanding by providing <Inclusion section="GSM.PackagingSpec.*" handlerRef="Customclass"/> in the config file we will get all the section id's to be validated but this is not happening for supporting documents. On debugging the sectioncontext object for packaging spec, I found that supportingdocuments object name is changed to SDMSupportingDocuments. I even added a separate inclusion tag ="GSM.PackagingSpec.SDMSupportingDocuments" along with another inclusion tag "GSM.PackagingSpec.*". so my config looks like this now:
<Inclusion section="GSM.PackagingSpec.*" handlerRef="Customclass"/>
<Inclusion section="GSM.PackagingSpec.SDMSupportingDocuments" handlerRef="Customclass"/>
Even then this did not work.
Please let me know if I am missing anything here.
It looks like when click the "Edit" button, section type id "GSM.PackagingSpec.SupportingDocuments" is not coming hence SLE is not working for supporting documents.
1. Could you modify
GSM.PackagingSpec.SupportingDocuments => GSM.PackagingSpec.SDMSupportingDocuments
in <P4P_Home>\config\Custom\CustomerSettings.config file.
2. Use GSM.PackagingSpec.SDMSupportingDocuments in SLESecurityExtension.config file
Then restart IIS, to check whether the change can work.
Thanks Ivy, will check and let you know.
I tried the steps suggested by you, but still the issue exists.
There is a SR(3-20425715871) to track the issue. Please follow the SR. I will give a workaround in the SR.