DDive11 - Novità Lotus Notes e Domino 8.5.3
•
1 j'aime•1,261 vues
Tutte le novità su Lotus Notes e Domino 8.5.3, previsto entro fine anno ed attualmente in beta chiusa. Vieni a scoprire tutte le migliorie e nuove funzionalità di questo importante rilascio. Una sessione di interesse per sviluppatori ed amministratori.
![Agenda ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Similaire à DDive11 - Novità Lotus Notes e Domino 8.5.3
Similaire à DDive11 - Novità Lotus Notes e Domino 8.5.3 (20)
Plus de Dominopoint - Italian Lotus User Group
Plus de Dominopoint - Italian Lotus User Group (20)
DDive11 - Novità Lotus Notes e Domino 8.5.3
- 1. Lotus Notes e Domino 8.5.3 Novità della nuova Release Soggetto a modifiche da parte di IBM in fase di rilascio della GOLD Release
- 3. Steve Jobs ci ha copiati iPhone iPod iPad Mettiamo i Puntini sulle «i»
- 4. Perché noi dal 2002 avevamo già…. Lotus iNotes
- 17. Novità Lotus Designer 8.5.3 Novità della nuova Release Soggetto a modifiche da parte di IBM in fase di rilascio della GOLD Release Change with your picture, add a 4pt border color 255,204,0 Cambia con la tua foto, aggiungi un bordo spesso 4pt colore 255,204,0 Please make sure that your slide deck renders fine in Lotus Symphony Per favore controlla che le tue slide si vedano bene con Lotus Symphony
- 34. The End
Notes de l'éditeur
- A new replication option, Enable Purge Interval Replication Control , on the Space Savers tab prevents older deletion stubs and document modifications from replicating to the application. Purge Interval Replication Control (PIRC) is a new replication setting which is designed to prevent old documents which may have been deleted from replicating back into a database after their deletion stubs have been purged. This problem has been encountered by many customers. The most common case occurs when an old version of a NAB (Domino Directory) is brought back online after several months or years. When this occurs, previously deleted person documents, group documents, server documents, and other design elements can replicate back into the environment because the deletion stubs have already been purged. PIRC prevents these documents from replicating back into the environment. How PIRC Works PIRC prevents documents from replicating back in two ways. The first is by modifying the 'since time' used by the replicator. If the server that is initiating the replication is release 8.5.3 and therefore PIRC-aware, then the algorithm to determine which documents qualify for replication has been changed to use the later of the PIRC date or the Since time contained in the replication history. This prevents the older documents from being replicated. Also, a DDM event is generated showing the number of documents skipped by PIRC. The second way in which PIRC prevents older documents from replicating in is by stopping the documents from being added to the database via NoteUpdate. This method occurs when a non-PIRC aware server is pushing older documents to the PIRC-aware server. In this case, NoteUpdate code will compare the SequenceTime of the document to the PIRC date. If the document is older, a DDM event will be logged and the document will be rejected. Note that the source server is unaware that the document was rejected. Therefore its logs will show that all documents were successfully replicated. However, the PIRC server will log the server name and the documents that were rejected, thus allowing the administrator to track down old replicas of the database and remove them from the environment. PIRC keys off the Cutoff date of a database. The cutoff date is the date when purge last ran. Purge is the process which removes deletion stubs from a database. Purge runs at one-third of the purge interval. So if the purge interval is set to 90 days, then a database may have deletion stubs up to 120 days old. Therefore PIRC will use this date to prevent documents older than this date from replicating into the database. If the cutoff date is not set in a database, which happens when replication history is cleared, the current date minus the purge interval is used.
- @GetMachineInfo( [Keyword]; "Needed for some Keywords string" ) Keywords: IsLaptop boolean return True if machine is a laptop, otherwise false IsDesktop boolean return True if machine is NOT a laptop, otherwise false IsSingleLogOn boolean return True if machine has Notes client installed with "single sign on", otherwise false IsMultiUser boolean return True if machine has Notes client installed as Multi-User, otherwise false HasDesigner boolean return True if machine has Designer client installed, otherwise false HasAdmin boolean return True if machine has Admin client installed, otherwise false IsStandard boolean return True if machine is running Standard Notes client, otherwise false MachineName string return Name of the machine boolean return True if MachineName string after keyword matches this machine's MachineName, otherwise false Memory number return Total amount of memory (RAM) DiskSpace number return Amount of free disk space Note: With this keyword, you can add a second parameter for the drive to scan for free space. If this parameter is not passed to the function, free space for the first (logical) drive - for example, drive C on Windows system - is displayed. Example: @GetMachineInfo([DiskSpace];"d:") EnvVariable string return Requires string of the variable name in Notes.ini to read, and returns the value of that ini variable or "" (null string) if not found SysEnvVariable string return Requires string of the variable name in system environment to read, and returns the value of that variable or "" (null string) if not found IP string/list return String representation of the IP address(es) in the form XXX.XXX.XXX.XXX , otherwise "" (null string) if not available boolean return True if pattern IP string after keyword matches this machine's IP address, otherwise false MAC string/list return String representation of the MAC address(es) in the form XX:XX:XX:XX:XX:XX , otherwise "" (null string) if not available boolean return True if MAC string after keyword matches this machine's MAC address, otherwise false Information for creating policy setting formulas Be sure all formulas have the correct syntax and can be compiled. Be sure values generated are correct in the context of the policy setting it is evaluated to. If the policy setting is text, then the formula should evaluate to a textual value. If the evaluation of the formula results in a type other than that of the setting, a mismatch error will be logged in the client's log and the setting will contain the default value, not the formula evaluated value. Use multiple conditions (if necessary) to ensure the formula is targeted at the correct machines/clients, and applied for the correct environment, and machine characteristics. The following are examples of how the formulas can be entered for the available settings. For the 8.5.3 client, these settings will be defaulted to the selected value for that setting, any formula provided will be evaluated and the result will overwrite or add the setting to the policy when it is read by the client. Clients older than the 8.5.3 version, will receive the selected default setting, and the formula will not be evaluated and the variable settings will not overwrite the defaults. Local Mail File and Managed Replica The values are "1", "3", "7" and "8" and the results of the formula must be textual and one of these values. "1" Create local replica "3" Create managed replica "7" Create managed replica or convert local replica to managed replica "8" Delete local replica or managed replica "0" Don't create local replica or managed replica (FYI: Someone needs to update the MMR doc to include this value too.) See Notes documentation for information on Managed Replicas and their supporting policy settings. Using the @UnAvailable as a formula result will make the setting not available.
- If "Require approval for device access" is enabled, and a user's device registers with the Lotus Traveler server, this policy checks to see if the user already has registered other devices. If the total count of registered devices including this one exceeds the "Number of devices to allow per user before approval is required", then the device is added to the Lotus Traveler system, but is not allowed to access any data until an administrator provides explicit approval for the device. When this occurs, if there is an email address or group name specified in the "Addresses to notify when approval action is pending", then the administrator and the user will receive an email indicating that an approval action is required before the device is allowed to use the system. To approve the device, the Lotus Traveler administrator opens the LotusTraveler.nsf application using the Domino Administrator client. In the Device Security view of this application, there is a new column called Device Approval which contains the device approval state. The administrator should select the action "Change Approval" to approve a device once they have confirmed that this is the appropriate action for this user.