Thank you for attending our recent webinar for robotics professionals on Wednesday, October 20 at 8:00 AM ET. This page will be updated soon with a recording of the event.

Description: In this 60-minute webinar, Pega Robotics engineers will show you how to leverage UI Connectors to extend Deep Robotics. This is a must-watch to take your career and bots to the next level. 

So, what's next?

Let's keep the conversation going! If you have any additional questions for Becky and Danny reply here to let them know.

We hope you understand we couldn't get to every question during our Q&A session, but we'd like to provide answers to as many as we can. 

Check them out below:

When writing an extension, how do you refer to the control, connector, or component you are extending in your code?

If you’re extending an Adapter control, use this.NativeControl to operate against the interrogated object. If you’re extending a non-Adapter control, like a variable or LookupTable, use this.Component. Note that this.Component is an IComponent type and must be cast to a specific type to access type-specific properties or methods.

Do you have to refer to the native control each place you use it, or can you assign it to a module-level variable?

You can assign it to a class variable if that is more to your liking.

Why would you use a component extension versus a type extension?

You would use a component extension if you’re building functionality that is specific to a single control and not desired for other controls of the same type.

Can you add events to a type extension? Where do you hook them up?

Yes, you can add events to a type extension, but you cannot listen to events on the NativeControl. You can listen to events on this.Component for extensions built against non-Adapter controls. To do so, subscribe to events on this.Component with the standard += convention. Event subscription can be handled in the constructor. You may also add new events to the extension that trigger by calling an extension method or changing an extension property.

Can you override a method on the type you are extending in an extension?

You cannot override a method on the extended type because the extension does not inherit from that type. The extension is a separate class, and its members are merely layered on top of the type and presented as a single entity in Robot Studio. Because of this, you should avoid adding members with the same name as a member on the extended type.

We tried the native control explorer in a project, and we came across that this is not able to read the properties for some controls. If this occurs what should be the approach or next steps?

This is normal for some properties that return complex types with no associated UI Type Editor (UI Type Editors are used to render values in the property grid). The property is still most likely accessible in an Extension or UI Connector. You can usually refer to documentation on the control author’s website to learn of its capabilities.

Can the UI Connector component be a built-on in Pega Dev Studio?

Yes, UI Connectors and Extensions can be built in Pega Dev Studio, though the IntelliSense is not as robust.

Thank you again for attending, and we hope to see you at our upcoming events.