Abstract: A method is used to manufacture an anvil of a surgical circular stapler. The anvil includes a head and a shank extending proximally from the head. The method includes forming the head of a surgical circular stapler using a metal injection molding process. The method also includes forming an annular array of staple forming pockets in the head. The method also includes machining the shank of the surgical circular stapler. The method also includes coupling together the head and the shank of the surgical circular stapler that were separately manufactured.

Abstract: Various techniques described herein relate to building and using representative data systems to store and manage representative profile data within contact centers. A representative data system integrates with external communication services and other internal/external systems to provide a uniform data store and interface to create and manage representative profiles. The representative data system retrieves and analyzes representative profile data during runtime contact center operations such as contact queuing, contact management, and/or workforce management. The representative data system may be implemented using relational or graph-based data structures to support advanced predictive modeling and impact analysis of scenarios such as service outages, dynamic workload shifting, infrastructure changes, and workforce changes.

Abstract: Spot aware print workflow techniques and system are described. In an implementation, a digital document is received for printing that includes a plurality of objects. Spot functionality is detected as corresponding to a respective object based on object properties detected for the respective object. One or more spot planes for are generated based on the spot functionality and a determination is made of color values for the one or more spot planes, respectively, based on context data describing a context, in which, the one or more spot planes are to be printed. The spot planes having the color values are output for printing by a print mechanism.

Abstract: Some embodiments provide a method for identifying competitors of a particular company. The method identifies a set of potential competitors of a particular company. For each potential competitors, the method calculates a score quantifying the competitive relationship of the potential competitor to the particular company. When the calculated score is above a particular threshold, the method associates the potential competitor as a competitor of the particular company.

Abstract: The present application relates to performing a scale-down of the computing resources allocated to executing a software application. For example, the software application for implementing a web server may be packaged as a container image, and one or more instances of the container images may be executed as one or more tasks. The individual tasks may be allocated a set of computing resources such as CPU and memory, and the incoming requests sent to the web server may be distributed across the tasks. If the volume of incoming requests drops below a threshold level, one or more of the tasks may be placed in standby mode, and the amount of computing resources allocated to such tasks may be reduced. When the volume of incoming requests returns above the threshold level, the amount of computing resources allocated to such tasks can be scaled back up to the full amount.

Abstract: Embodiments of the invention are directed to systems and methods that enable authentication of a user via an authentication application that is different than a wallet application that is being used to process a transaction. The wallet application may contain payment devices and/additional wallet applications.

Abstract: The present application relates to performing a scale-up of the computing resources allocated to executing a software application. For example, the software application for implementing a web server may be packaged as a container image, and one or more instances of the container images may be executed as one or more tasks. The individual tasks may be allocated a set of computing resources such as CPU and memory, and the incoming requests sent to the web server may be distributed across the tasks. If the volume of incoming requests drops below a threshold level, one or more of the tasks may be placed in standby mode, and the amount of computing resources allocated to such tasks may be reduced. When the volume of incoming requests returns above the threshold level, the amount of computing resources allocated to such tasks can be scaled back up to the full amount.

Abstract: Various techniques described herein relate to a client application framework for a contact center environment. A role-specific thick client framework may include a web browser-based application having multiple processes that can be distributed across the computing infrastructure of the client device. A portion of the framework may include a container application image received from an internal server of the contact center and launched by the client device. The framework also may include queuing and communication services executing on the client device, which interface with the internal client application and external service providers to support a common queuing framework and an integrated model implementation across the contact center environment.

Abstract: Techniques described herein relate to a client application framework for a contact center environment. A role-specific thick client framework may include a web browser-based, desktop application having multiple processes that can be distributed across the computing infrastructure of the client device. A portion of the framework may include a container application image received from an internal server of the contact center and launched by the client device. The desktop application may collect data associated with use of the container application image and transmit the collected data to a contact center server. The contact center server may process the data, in some instances along with data from additional desktop applications on additional client devices, to implement one or more integrated models across the contact center environment.

Abstract: A biological specimen of a subject is handled and tracked for a procedure involving that specimen. Prior to initiation of the procedure, a first procedure data structure (PDS) is generated. The first PDS binds an identifier corresponding to the subject with an indicator of a procedure to be performed on the specimen and identifiers of a specimen container and a specimen holder that physically contacts the biological specimen, as well as a scheduled time for the procedure. A schedule of a plurality of PDSs including the first PDS, is displayed on a display device of a graphical user interface. Following initiation of the procedure, the first PDS is updated based on user input, and after the procedure, at least a portion of the first PDS, as updated, is stored in a database in conjunction with other PDSs respectively associated with other completed procedures.

Abstract: The present invention provides a robust and effective solution to an entity or an organization by allowing to visualize the flow of automotive data signals from a source system to a sink system with different metric signals at each step and creating a mechanism for creating automotive signal quality marker (ASQM) for high quality automotive data signals by determining high value data parameters, inter-parameter correlation, data quality variation with trip duration, and frequency of data collection/distribution across datasets. The quality criterion thus developed is applied to data generated from a plurality of data sources. The ASQM may be calculated by converting the developed automotive data signals quality criterion into a numeric value on a specified scale. It can be used by all stakeholders in the value chain for consistent measurement of automotive data signals quality.

Abstract: Techniques described herein relate to message distribution in a contact center. Messages generated by an administrator and/or by a trained model processing data from customer interactions with the contact center are stored in a message queue. A desktop application running on a representative device and hosted by the contact center queries the message queue for messages intended for a representative using the representative device. Messages intended for the representative are automatically displayed on the representative device, e.g., on the desktop.

Abstract: Data is collected from a set of devices according to a data collection policy. The data is associated with at least one of: device configuration, device state, or device behavior. A norm is established using the collected data. A different data collection policy is established based on the norm. Data is collected from a particular device according to the different data collection policy. The norm is compared to the data collected from the particular device. If there is a deviation beyond a threshold deviation between the norm and the data collected from the particular device, a responsive action is taken.

Abstract: Techniques described herein relate to a client application framework for a contact center environment. A role-specific thick client framework may include a web browser-based, desktop application having multiple processes that can be distributed across the computing infrastructure of the client device. A portion of the framework may include a container application image received from an internal server of the contact center and launched by the client device. The desktop application may collect data associated with use of the container application image and transmit the collected data to a contact center server. The contact center server may process the data, in some instances along with data from additional desktop applications on additional client devices, to implement one or more integrated models across the contact center environment.

Abstract: A customer relationship management (CRM) platform may use data objects to store data associated with a virtual meeting. The CRM platform may store information about a virtual meeting in a meeting object, and store information about meeting participants in participant objects linked to the meeting object. The CRM platform may also store meeting information, returned from a separate virtual meeting platform that will host the virtual meeting, in the meeting object and the participant objects. Accordingly, the CRM platform can use the meeting object and participant objects to display meeting information in a user interface, allow users to edit meeting details via the CRM platform, and/or allow users to join the virtual meeting via the CRM platform without separately logging in to the virtual meeting platform.

Abstract: Updates to projected data subsets may be ordered using conditional operations. When updates to a data set are received, a determination is made according to a schema for a projected subset of the data set as to whether the update is to be propagated to the projected subset of the data set. If the update is to be propagated, a comparison of a version identifier for the update may be made with a version identifier for the subset to determine whether performance of the update is consistent with an ordering of updates performed to the first data set. If the comparison indicates the performance of the update is consistent, then the update may be performed to the projected subset. If not, then the update may not be performed.

Abstract: Aspects of the present disclosure relate to modularizing and embedding modules across a variety of web applications. More specifically, the present disclosure provides an adaptive UI module to web application servers that adapts its format upon evaluating an environment of the web application and receiving a user request for supplemental information. For example, a single adaptive UI module may be used across a variety of web applications, with a variety of requests for supplemental content from within each web application, to generate multiple, unique formatted UI modules. In this way, a single adaptive UI module may generate formatted UI modules specific to the formatting requirements of each requesting web application, with supplemental content related to each unique user request from within each web application.

Abstract: Offline building of a projected data subset may be performed. A request to create a data set that is a projected subset of data from a source data set may be received. A data store separate from the data store storing the source data set may store a copy of the source data set that is used to replicate items to the projected subset of data according to a schema for the projected data subset. Updates made to the source data set may also be replicated to the projected data subset according to the schema. Conflicts between replicated items and replicated updates to the projected data set may be resolved by comparing a version identifier for the replicated update and replicated item to determine what to store in the projected data subset.

Abstract: A device receives network condition information. The network condition information is indicative of network resource availability at a plurality of locations. The device processes the network condition information to associate network resource availability identified in the network condition information with one or more airspace voxels that represent one or more three-dimensional (3D) portions of airspace corresponding to the plurality of locations. The device receives flight parameters relating to a proposed flight plan of an unmanned aerial vehicle (UAV) through airspace represented by a set of airspace voxels, and network performance parameters associated with the proposed flight plan. The device determines that the network resource availability that is associated with the set of airspace voxels fails to satisfy the network performance parameters, and performs one or more actions to enable the UAV to access network resources that satisfy the network performance parameters.

Abstract: A customer relationship management (CRM) platform may use data objects to store data associated with a virtual meeting. The CRM platform may store information about a virtual meeting in a meeting object, and store information about meeting participants in participant objects linked to the meeting object. The CRM platform may also store meeting information, returned from a separate virtual meeting platform that will host the virtual meeting, in the meeting object and the participant objects. Accordingly, the CRM platform can use the meeting object and participant objects to display meeting information in a user interface, allow users to edit meeting details via the CRM platform, and/or allow users to join the virtual meeting via the CRM platform without separately logging in to the virtual meeting platform.