Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ALIM | Exor
  • Product Communities
  • AssetWise
  • ALIM | Exor
  • Cancel
ALIM | Exor
ALIM | Exor - Wiki The [Code to Execute] field in the Process Types form is read-only
    • Sign In
    • -Exor - Wiki
      • +ALIM Document Manager
      • An Attempt to Reset Your Password Has Failed
      • -AWLRS
        • AWLRS and Spatial Manager - Questions and Answers
        • +AWLRS 1.3.x versions
        • +AWLRS 1.2.x versions
        • +AWLRS 1.1.x versions
        • -AWLRS Troubleshooting
          • exporting a shapefile from AWLRS and Importing into ArcMap sometimes produces a blank attribute table
          • AWLRS error: the node id of the node could not be retrieved.
          • A New Layer Doesn’t Appear In Maps
          • Layer or part of a layer disappears after enabling Edit
          • Node error messages when editing in AWLRS
          • AWLRS login window is not displayed
          • 'Invalid Attribute supplied' error in the Advanced Search dialog
          • After an unsplit or an unmerge I don't see any changes to the parent route members
          • AWLRS : Cannot locate asset on network type.
          • AWLRS is not working: Network or configuration error
          • AWLRS More rows to export
          • AWLRS: export is showing error: OGR Error. Attempt to write feature failed.
          • AWLRS: export to scv is showing error: PLS-00103
          • I can't see the cursor blue dot when I digitize a datum
          • The error “An Internal Server Error occurred. [object Object]”
          • The [Code to Execute] field in the Process Types form is read-only
          • User is unable view the network.
          • ORA-20000: Upgrade of "AWLRS" from v x.x.x.x t v y.y.y.y not allowed
        • Learning
        • +How To
        • Resolve potential date / time issue in the Exor database
        • +Transportation Data Loader
      • +Exor Asset Manager
      • +Exor CIM / FIM
      • +Exor Document Manager
      • +Exor Enquiry Manager
      • +Exor Information Manager
      • +Exor Information Manager TMA Reporting Pack
      • +Exor Maintenance Manager
      • +Exor Maintenance Mobile
      • +Exor MapCapture
      • +Exor MapCapture (ESRI)
      • +Exor MCI MapCapture Interface
      • +Exor Network Event Manager
      • +Exor Network Manager
      • +Exor Oracle
      • Exor Problems and Solutions
      • +EXOR product placeholder
      • Exor Public Enquiry Manager API
      • +Exor Schemes Manager
      • +Exor Spatial Manager
      • +Exor Street Gazetteer Manager
      • Exor Streetworks Manager
      • Exor Streetworks Mobile
      • +Exor Structures Manager
      • Exor Structures Mobile
      • +Exor TMA Noticing Manager
      • +Exor TMA Permitting Manager
      • +Exor UKPMS
      • Remove @ from the AWLRS Local Password Policy
      • +Transportation Intelligence Gateway
      • Unable to connect to Power BI dataset
      • +Video Series for Exor
      • Working From Home with Exor
    • +AssetWise ALIM for Transportation
    • How To Import SSL Certificate 11g Weblogic

    You are currently reviewing an older revision of this page.

    • History View current version

    The [Code to Execute] field in the Process Types form is read-only

      Product(s): AWLRS
      Version(s): 1.2.x-1.3.x
      Environment: N/A
      Area: Other
      Subarea: N/A

    This is by design due to security considerations. 

    AWLRS provides screens to manage processes and their execution. This is mainly intended for observation and limited management. Currently Exor Forms still provide more capable functionality and can still be used for the detail where AWLRS does not support a particular aspect. Process scheduling and management is also under wider review as part of the journey to use databases other than Oracle.

    With the current release of AWLRS the intention is to provide a process management tool to satisfy the majority of daily use cases, to avoid users needing to use different tools throughout the working day. However, some aspects have been intentionally limited (for example made read only) in AWLRS until other mechanisms are developed. The reason for these limitations is ultimately to ensure the security of the database and the information it stores.

    AWLRS potentially expands availability to a wider audience of users, as it is web based and does not need complex installation or deployment. It is incumbent on Bentley to ensure the software is not open to exploitation should access fall into the wrong hands. The ability to modify database code is one such area of concern, damage to the data through accidental or intentional acts is something we are actively trying to avoid. SQL injection are a prevalent attack vector and one of many we are doing our utmost to protect our users from. As a result some working practices will need to adjust to adapt to a strengthened approach in the way the database is used.

      Original Author: NT
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies