Skip to main content
P
ptc-46688181-Visitor
1-Visitor
April 24, 2015
Solved

unable to access DEFAULT_END_TIMESTAMP

  • April 24, 2015
  • 1 reply
  • 3341 views

I implemented a version of the Groovy script shown on the MobileLocation API Reference page as a Custom Object on the Axeda Platform.  I get the following exception when I run this script:

 

Access to property DEFAULT_END_TIMESTAMP of class com.axeda.drm.services.mobilelocation.MobileLocationImpl not allowed

 

What is the proper reference to the DEFAULT_END_TIMESTAMP property?

    Best answer by ptc-4668818

    It appears that a workaround is available for this issue.  You don't need "lake" access if you know that DEFAULT_END_TIMESTAMP = 4136677158944L.

    1 reply

    C
    ckaminski5-Regular Member
    5-Regular Member
    April 27, 2015

    That API is located in the 6.8 Code Access Policy (CAP) level "lake."  By default all new instances in the On-Demand Center are provisioned in "pond."  "Lake" and "Sea" are progressively more permissive depending on your application requirements. 

    I recommend opening a support case to have your CAP level altered to lake. 

    -Chris Kaminski

    PTC Customer Support

    P
    ptc-46688181-VisitorAuthorAnswer
    1-Visitor
    April 30, 2015

    It appears that a workaround is available for this issue.  You don't need "lake" access if you know that DEFAULT_END_TIMESTAMP = 4136677158944L.

    C
    ckaminski5-Regular Member
    5-Regular Member
    May 1, 2015

    I almost posted that very answer - for while this is true, I'm always leery of recommending someone rely on implementation details like this.

    Regards,

    -Chris Kaminski

    PTC Customer Support

    Terms & ConditionsCookie settingsAccessibility statement