Microsoft Technology Licensing, LLC

Sai Shankar

Ashish Kumar Singhal

Rakesh Gupta

Jagdish Singh

Satish Kumar Chittamuru

Arvind Kumar Krishnan

Namendra Kumar

Burra Gopal

Rolando Jimenez Salgado

David Koronthaly

Patrick Dengler

Sushil Kumar

Lawrence M Sanchez

Ricard Roma I Dalfó

Himesh Shah

Zoltan Pekic

Pankaj Lohumi

Nabarun Mondal

Shyam Sundar Jayshankar

A test framework for automating multi-user, multi-step and/or multi-machine test cases for electronic calendaring application objects is provided. Test cases may be automated where coordination between a number of machines is required to test electronic calendaring application user scenarios. In addition, automation of multifold interaction between two electronic calendaring application users is provided.

Test framework for automating multi-step and multi-machine electronic calendaring application test cases

Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it is sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.

Metadata driven user interface

Recurring appointment items in a calendaring application are synchronized and recorded in a backend Line Of Business (LOB) service. Items marked in the calendaring application for time recording are used to create a recurring bound item with extended properties. A sweeper module scans on every run the mailbox for such recurring bound items. Occurrences of bound recurring appointments, which occur between the last scan and the current scan, are determined and detached from the corresponding recurring series, such that standalone bound items, are created for such occurrences that can be recognized by an LOB application. Entries for bound items are retrieved from a client data store and synchronized it with the backend LOB service through a create, update, or delete operation request.

Achieving recurring item recordings from calendaring applications over LOB systems

Growing community of inventors

Hyderabad Telangana, India

Sai Shankar