SignMeeting JOOXTER

RELEASE NOTE

2017-07-12 V1.12.27 download

BUG FIX, NEW FEATURES, MINOR UPDATES
  • Change: improve resource drag'n drop accuracy to support properly SMH300/SLATE106 devices
  • Change: when a new device is newly registered, a screen is prompted to enter the appropriate layout for this new device (default: Room screen or Room label)
  • Change: some JOOXTER meeting could be not displayed if some optional fields was not filled in JOOXTER calendar
COMPATIBILITIES
  • Screen Composer V3.11.11 (or above) Not compatible with Screen Composer V2.xx.yy
  • Gekkota 3.12.25 (or above) (for the last features regarding SignMeeting, especially for modulation display capability)
  • SMT210 platform (for Room screen layout, touch screen, RFID badge detection)
  • SMH300 (for Room label layout)
  • DMC200, SMT210, SMA200, SMP200, SMA300, DMB300, WINDOWS platforms (for Summary screen by event or Summary screen by resources layouts)
  • LDAP V3 (used by Windows Server 2000/Active directory and above Windows Server version)
  • Briva LDAP

INFORMATION


DOCUMENTATION

CSS FILE FOR TAB STYLE

UPGRADE VERSION

  • In order to upgrade:
    • open Screen Composer,
      • click on SignMeeting link to configure the app
      • make a modification (ex Title) and
      • click on "finish" button
      • click again on SignMeeting link (version modification should be noticed)

DATASOURCE HOSTED ON DISTANT SERVER

  • Some slowness could be noticed when booking (or cancelling) a meeting in case datasource is referring to distant server with poor reaction capability

NOTE WHEN FORMULAR CAN NOT BE OPENED IN SCREEN COMPOSER

  • In some rare case (seen most of the time after version upgrading), the SignMeeting formular could not be opened in Screen Composer, and a message is displaying: An error occured while opening the interface. To solve the issue close and open again Screen Composer

NOTE WHEN PLAYER IS FACING ISSUE TO CONNECT CALENDAR SYSTEM

  • In case the player INNES does not manage to resolve domain (for example https://.com/), SignMeeting can raise a message A problem occured during the initial server connection / Details: xhr.status 0. To solve the issue, in the player WebUI, configure server DNS with Google DNS server and try again
    • Prefered primary DNS server: 8.8.8.8
    • Prefered secondary DNS server: 8.8.8.4

NEXT MEEETING TO CURRENT MEETING

  • In some rare cases, event pass from next meeting to current meeting in late. If the occurence of this problem becomes to be annoying, decrease datasource/refresh time to work around

NOTE FOR CSS CLASS

  • CSS file need to be configure to suport CSS class
    • (if required double check relative path of picture in theme_css_generic-V1.10.12.css)
    • rename if required the .cusClass1 into the name you want
    • choose API inside
      • background-image or background-color
      • Note: CSS is compliant with Mozilla CSS background API (W3C)
        • https://developer.mozilla.org/en-US/docs/Web/CSS/background
          • background-image
          • background-position
          • background-size
          • background-repeat
          • background-origin
          • background-clip
          • background-attachment
          • background-color
    • for example:
      • The file theme_css_generic-V1.10.12.css is situated in a sub-directory css (./css/theme_sm.css)
      • The file background picture is situated in a sub-directory images (./images/diagonal3.png)
      • Relative path has to be in this case
        • background-image: url("../images/diagonal3.png"); (go up to CSS file parent directory and then go to images directory
  • Match SignMeeting device/edit/CSS class value with a value of your theme_css_generic-V1.10.12.css
    • for example, when .cusClass1 is present on theme_css_generic-V1.10.12.css
      • enter cusClass1 in device/edit/CSS class field
  • Add the required media ./images/diagonal3.png in Screen Composer manifest (medias tab)

OLD VERSIONS HISTORY


2017-05-22 V1.12.26 download

BUG FIX, NEW FEATURES, MINOR UPDATES
  • Initial release