Hi Team,
For using the function a!documentViewerField() in On-premise environment for above 18.3 versions, It is showing "Missing system configuration", so we tried to change in custom.properties file as per the Documentation given, still it is showing as "Missing system configuration". Please find the attached screenshot.
Any help, would be appreciated.
Regards,
Krishna.
Discussion posts and replies are publicly visible
Thanks for your response, Jackie Jubien. But they have given,
conf.suite.STATIC_SERVER_AND_PORT, conf.suite.DYNAMIC_SERVER_AND_PORT, and conf.suite.SERVER_AND_PORT are all unique. So how should we give values for static and dynamic port. or can we provide the same as in the SERVER_AND_PORT for both static and dynamic.
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT
conf.suite.SERVER_AND_PORT
Depending on whether you have a standard or non-standard set-up, you will have to create your URLs similar to the way the documentation explains:
Example when using a standard top-level domain like .com or .co.uk:
.com
.co.uk
1 2 3
conf.suite.SERVER_AND_PORT=www.example.com:8080 conf.suite.STATIC_SERVER_AND_PORT=www.example-static.com:8080 conf.suite.DYNAMIC_SERVER_AND_PORT=www.example-dynamic.com:8080
Example when using a non-standard top-level domain like .corp:
.corp
1 2 3 4
conf.suite.SERVER_AND_PORT=www.example.corp:8080 conf.suite.STATIC_SERVER_AND_PORT=www.example-static.corp:8080 conf.suite.DYNAMIC_SERVER_AND_PORT=www.example-dynamic.corp:8080 conf.suite.conf.suite.DISABLE_STRICT_DOMAIN_SECURITY=true
Keep in mind the port may be different depending on whether you are using HTTP or HTTPS. Another thing to consider, is that since you are setting up two new domains, if you are utilizing white-listing you will have to allow those domains.