Be.Smart ERP Connector
(EN) Consultant Manual
(EN) Consultant Manual
  • Be.Smart ERP Connector Consultant Manual
  • Abbreviations used
  • Home
  • Purpose of the product
  • Technical solution
    • Data Interface
    • Autodesk Vault
    • Basic types of jobs and their origin
  • Configuration
    • EC configuration (central)
      • Main Card
      • Property Values tab
        • Tab < entity>
    • EC local configuration
    • Logging in
      • Logging to the local station
      • Logging in DI
    • Reverse logging
      • Description of the reverse logging process
    • FLAGs (additional flags in std Vault configuration)
      • List of symptoms
  • Commands and Features in Vault Explorer
    • Attach to already existing purchased item
    • Apply item security to files
    • Create Raw material BOM rows
    • Send to DI (Send to Data interface)
    • Data interface browser
      • Functions
  • Export
    • Item breakdown
      • BOM loading method
      • Transfer MJ
    • Atypical requirements
  • Imports
    • Processing of external requests for transfer to Vault (from version 2019 inclusive)
      • The procedure for processing the Arkance.Import initialization job:
    • PreProcess sample
    • Imports of entities
      • Entity identification by ERP system
      • Import items
      • Importing applications
      • Import folder
      • Importing a change command
      • Import schedules
  • Recommended commissioning procedure
    • DI commissioning
    • Mapping fields
  • Castomization (ec addons)
  • Attachments
    • Job types - complete list
    • Configuration type Global/Workgroup
Powered by GitBook
On this page

Was this helpful?

  1. Configuration

EC local configuration

The local configuration is updated from the central configuration - there is no point in changing it manually !

  • is stored on the local station: %Public%\Documents\CadStudio\ErpCnn2g\<VaultServerName>\<VaultName>\ErpCnn2g.local.config

  • the update takes place when you log in to the Vault and execute the command that is part of the EC

  • purpose = provides information to VaultExplorer at startup, before the user logs in to Vault - i.e. at a time when the central configuration is NOT yet available; this is how Autodesk's programming interface for this application (Vault API) is created

  • therefore, the necessary part of the central configuration, which was available at the last login to the Vault, is written into the local configuration - it is:

    • a list of all commands programmed and their location or availability in the VaultExplorer menu structure

    • list of bookmarks and their context

  • the contents of the local configuration can be useful for troubleshooting (e.g. why a programmed command is not visible)

PreviousTab < entity>NextLogging in

Last updated 2 years ago

Was this helpful?