Release Notes

Keystore import is now supported via Microchip manifest, meeting specific client requirements.

Fixed the issue of incorrect total count (Keystore + Device) in the KeyStore module.

CA Signed Certificate and CA Signed Individual Certificate have been moved into x509 for better management and allocation of devices.

Updated software and hardware template for X509 merging, ensuring seamless certificate-related changes.

Multi-Platform Support: The Subscription Portal now offers subscription solutions on both Azure and AWS platforms, providing users with versatile options.

CPID Search: Users can now easily search for consumers using CPID, streamlining the consumer management process.

A new Status Filter has been added to the Connect Studio Solution's filter list. Users can now filter solutions based on their active or inactive status, enhancing solution visibility and management.

Partners can use AWS connectors to securely connect their on-premises and cloud-based databases to AWS services. AWS connectors are available through subscription plans in the Product module. Also, consumers can view the related configuration in IoTConnect.

Partners can now view consumption of the package by their consumers for the plans created with AWS services in the Consumer module.

In Subscription portal, all the subscription plans are created on AWS services. Hence, new subscribers can subscribe to plans created on AWS services only.

In Device Management module, partners can manage and unmanage devices with IoTConnect AWS services.

Message Version 2.1 helps improve the reliability and security of templates. This is because it has been thoroughly tested and vetted by a large community of users and developers. Templates created in AWS Instance for software product in the Product module or in the DMS module must use Message Version 2.1.

SQS is a highly scalable and performant messaging service that can handle a large volume of messages without impacting the performance of the IoT product. We have added SQS configuration in the Product module for AWS Environment in the Configuration tab.

In ExpressConnect module, partners can create designs only for Azure products.

In Device Management module, partners will not be able to select ExpressConnect checkbox for their AWS products as it is not currently available.

Partners can manage their devices associated with the AWS environment in the DMS module, including allocating, managing and deleting them.

Partners now have the ability to create, delete and manage/unmanage the devices they own within the AWS IoT Core Service Provider account. This empowers partners to efficiently oversee their device ecosystem. By clicking on "View" button, partners can access and review their account details.

We have implemented AWS software packages for partners through the Software Service. Partners can seamlessly use these packages to create AWS production environments for their products. This streamlines the software management process, making it more efficient and user-friendly. These packages are thoughtfully curated to facilitate the creation of robust AWS production environments tailored to their specific product requirements.

We have temporarily concealed the "Connectors" option within the Subscription segment when creating a plan in environment from an AWS instance. This adjustment has been made to ensure a smoother user experience. Rest assured, we remain dedicated to enhancing this feature in further developments.

The data type of a sensor value determines how it is interpreted and processed. If the wrong data type is entered, the sensor value may not be interpreted correctly or may even cause errors. Hence, to avoid such errors, we have included Message type 2.1 along with Message type 1.0. It allows partners to enter sensor value in bit, Boolean, date, datetime, decimal, integer, latlong, long, object, string and time. This is added in Device Management and Product modules.

In the IoT Service Providers module, we have added AWS IoT Core as a service provider. Partners can now be independent of IoTConnect and choose their own IoT platform with this service.

Partners can enter umlaut characters in Consumer module. This allows them to ensure the authenticity of their company’s name.

In Device Management module, partners can now view the service provider for their managed devices.

Partners can view certification type in the Import Batch History segment from Device Management module.

Partners can have a unique KeyStore ID throughout the Partner Program portal.

Partners can now mange and allocate Authentication Type 7 - CA Signed Individual certificate to their device in Device Management module.

Partner can enter special character, for their users and consumers in first name and last name field throughout the Partner Program portal.

Device management package details have been removed from Partner Services module. You can now select package while creating IoT service provider.

We have added a module for KeyStores in the help wizard. You can refer to it when you need any help regarding KeyStores.

When you create a ticket in support module, the email that you receive will display the name of your company along with other details.

Partners can enter their email addresses that are long. We have increased the character limit to 100 characters. This applies to all modules within the portal.

Users will receive an email that includes their name as well as the name of their company when they sign up on the Partner Program portal and become a partner.

Partner Program offers AppConnect module where you can use ready-to-deploy solutions that can be customized as per the defined use case. We have implemented the launch configuration for Genset Monitoring, Fleet Management and Greenhouse solutions so you can access the full potential of the solution and explore its working.

We offer a detailed consumer invoice as a proof of a transaction. This ensures accuracy, transparency, facilitates payment information and builds trust among both the parties.

Users will receive an email when their plan expires. They will also receive a reminder email for auto-renewal.

In Partner Program portal, when a partner user is created, DevLab is the default role associated with the user. Admin or Owner can later assign a different role. There can only be one partner user with Owner or Admin role in IoTConnect.

A template is already associated with every pre-defined solution in AppConnect. Each template has a unique ID. Users can now view TemplateGUID from the Environment module.

We aim to create portal that is easily accessible on a wide range of devices, from desktop computers to smartphones and tablets. Hence, the registration module of Subscription Portal is now mobile responsive.

Partner Program offers AppConnect module where you can use ready-to-deploy solutions that can be customized as per the defined use case. One such solution is Smart Asset Management. We have implemented the launch configuration so you can access the full potential of the solution and explore its working.

It is essential to place apt breadcrumbs for easy navigation. Considering it, Partner Program has made changes to the breadcrumbs in all its modules. Now, partners will better understand where they are in Partner Program.

We redesigned the page with a better UI in the consumer module. Now, partners can modify or cancel their plans with ease.

Previously, Partner Program offered a toggle button to allow users to change between the old and latest UX. We removed the toggle button as all users will experience the newest UX now.

IoTConnect Instance webpage was not accessible in previous theme, but with new theme implemented, Partners can now access IoTConnect Instance webpage for better usability.

Partners can now access subscription plan module from Marketplace, while editing the subscription plan.

Partners can hide/show products in the Marketplace module. They can temporary hide their products and display them as per their requirements.

Earlier there was no package code provided in consumer details but now, Partners can manage Consumer module by adding package code.

Partners can now search with package code from consumer listing.

Previously, our partners had an option to associate with multiple types. For example, a device type partner can also be an OEM partner. However, to simplify processes, only one partner type will be associated with one partner.

Earlier the limit for allocating messages was 1000 messages per day. However, the limit is now set from 1 to 1 billion per day.

Several modules of Partner Program are only accessible in the new UI. Hence, from 17th August 2022, onwards the old UI will not be available. The toggle button to switch UIs will be disabled.

When a partner creates a ticket, the users associated with that partner will receive an email. Previously, they did not have an option to attach the ticket link in the email. Now, they can share the ticket link as well.

A user created by the admin partner can edit the tickets that are created by them. They can view tickets created by other users but will not be able to edit them.

For ease of use, notifications will not open in a separate page. When a partner clicks on the bell icon, they will get notifications list as a scroll-down list. They can check the full list of notifications by scrolling.

If the information in any modules is not filled, i.e., the fields that are mandatory to be filled are empty, and if the partner continues to save the form, Partner Program will highlight the empty required field. Also, if a partner is in the process of filling a form and clicks on another module without saving the information, they will get a pop-up asking if they wish to save the changes.

When a user gets an email regarding the services they can avail, they will also receive information related to their trusted partner.

Help and support module has been modified to simplify the access to relevant topics. Partners can now easily create and manage tickets with just a few clicks and fill in the details for modules like Partner Program, IoTConnect and more. Help and Support are now two separate modules that partners can easily access from the top right corner of the portal.

In Role module, we have updated the product segment by adding ability to manage access for billing engine. This applies to services, solutions and OEM type partners.

We have implemented notification preferences user and role-wise. This enables partners to set alerts for users or specific roles according to their requirements.

When pressing Enter key at any form in any module, it would direct partners to submit button. We have changed this. Now, partners will move to the next field in the form by clicking Enter.

In Solutions Hub module, we have changed the terminology from ‘Add Solution’ to ‘Add Product’ to reduce complexity for better understanding.

The ticket package in the support module has a default selection based on the product that you select to create a ticket for.

Previously, partners could not download their product lists. You can now download hardware and software product lists in CSV format.

Improved API performance by reviewing azure app insights. Spin up Azure SQL auto performance tuning to improve database performance.

Enabled Azure application insights for all API projects to analyze overall performance.

Partner’s device test run log and approval has been enhanced.

Partner Program now allows you to identify a certified product in the product list. Till now, the product list presents that whether the product is software, hardware, or AI model. And whether it is system generated or products created by admin. Now, the product list shows whether the product is certified or not. Thus, it saves significant time and delivers essential information.

Solutions Hub is a dedicated marketplace for all IoT products and services. You can add your smart solutions and products in Solutions Hub to showcase them to the global market. We have added Solution Hub as a separate module in Partner Program. Now, you can access Solution Hub easily from the left menu.

Get a complete view of IoTConnect health for all your shared instances from instance.

You can now use more than one IO Expanders while creating a design in ExpressConnect.

To help users quickly understand which page or higher-level category they are on and how they got there, Partner Program has added breadcrumbs with a sticky header.

Previously, Partner Program was offering entity management, role management and my services separately. Considering the increasing number of features Partner Program being added, we have merged entity, role and services in Setting to compress the left menu. However, when partners click on entity or role, they will be redirected to entity and role pages respectively.

We have made the IoTConnect DevLab page more user-friendly. Now, you will find IoTConnect DevLab and AppConnect on this page. Moreover, in the IoTConnect DevLab tab, we have added technical details. While in the AppConnect tab, you can filter the products using the AppConnect type and category.

Earlier, DevLab permission was not a primary requirement. It has now been removed from IoT management permission and set as mandatory for creating a Sub-Partner.

Sub-Partner will receive an email about their DevLab creation. Along with Partners, now they can also log in to Partner Program. Sub-Partner user type will stay as ‘Admin’ by default. Sub-Partner will also get access to their DevLab from the Product page.

Partner Program now enables you to configure solutions to import, transfer, load and process data from various sources at the solution level. Solution configuration allows partners to sync IoTConnect module data with their cloud or on-premises storage.

To enhance the user experience, we have converted the ‘My Consumers’ page into three tabs. It delivers meaningful information like company name, consumer type, email and so on. In case if any device is attached to the consumer, it will also be showcased.

An email notification is triggered when an email address is changed. That email notifies the user that the email address has changed. Now, the email also communicates the first name and the last name of the person who made the change. Moreover, the email reaches to both the persons – one who is updating the email and the other who is becoming a primary contact person.

In line with our efforts to provide all details in one place, we have added an ‘instance type’ in the consumer list and detail page. It enables partners to know which instance type a consumer is using.

Considering different needs of each partner, we offer services. From Partner Program services, you can avail any module for a month, quarter or year. This allows you to check whether you need hardware-related services or software-related services. If you opt for hardware services, you will not need access to read/manage environment for your core business. Partner Program has modified certain access based on services you choose. Now, you will get access to read/manage environment only if you choose software services. The modification is regarding the usage of the service after a particular segment of the module is exhausted. We provide a cap of certain percentage as per the requirement for partners to continue to avail that service even after they have exhausted it. For a detailed understanding of services, you can refer this article.

Previously, consumers were not getting device allocation from hardware products. Now, Partner Program allows allocating devices from batch import. A user can allocate any batch of hardware devices to the consumer. Partners will also see the device activity logs and device allocation history of each consumer in the hardware product.

While uploading devices in bulk, Partner Program asks users to upload JSON file. The file requires a CSN. Partner Program has introduced the validation feature of that CSN now from 1 to 95.

In the menu, ‘Services’ has been renamed to ‘My Services.’

Earlier, ‘Help & Support’ was accessible from the Partner Program menu. Now, it is reachable from the top-right corner. The icon for ‘Help & Support’ can be found between the notification icon and the username icon.

To serve you better in raising and tracking tickets, we have shifted the ‘Tickets’ in the ‘Help & Support’ page. ‘Tickets’ shows new tickets, on hold tickets, resolved tickets and tickets list. Tickets list presents columns like number, title, assignment group, status, created on, updated on and actions. The list gives you an eagle-eye overview of your tickets and it can now be accessed easily from the ‘Help & Support’ page.

Previously, in consumption messages, the last three zeros of four-digit numbers used to be represented with the letter ‘K’. Now, to maintain consistency, in three-digit numbers, the last two zeros are also presented using the ‘K’ letter. For example, 500 will be displayed as 0.5k.

Earlier, IoTConnect user counts and device message counts used to be shown in round figures in ‘My Services’. Now, no round figures are going to be used. The zeros will be presented using letters like ‘K’ or ‘M’. For example, if you have utilized 100 messages, it will be shown as 0.1K in ‘Utilized Messages.’

We have upgraded our help wizard widgets for a better familiarizing experience.

Earlier, admins didn’t have direct access to information like the number of connected devices to IoTConnect, partner-wise consumption data, the top 5 consumers and the latest/new consumers. Partner Program now permits admins to access this information.

Previously, account managers, admins, or partners could not see messages and D2C data consumption from the dashboard. This gives Partner Program stakeholders handy access to messages and D2C data consumption, which saves time and efforts.

While onboarding, before you click the submit button and send us your application, you can now add a user email to send the Docusign agreement to an authorized person. Once the document is signed, the onboarding process will continue.

We have a six-step process to onboard a partner, out of which the third step is compliance check. This is where you need to upload certain required documents which are mentioned on the screen. Once uploaded, a compliance user verifies it. In any case, if a compliance user rejects the details and your document stays unsigned, the onboarding process will maintain the ‘In Progress’ status. That status will only progress when you upload the latest documents and they are verified.

Partner Program will now keep the same number of emails for watchers and Account Managers. Whether it is about creating, submitting, compliance approval, or account manager approval emails – watchers and account managers will get the same number of emails from now on.

In cases where an Account Manager is inactivated, Partner Program will allocate another account manager to the Partner based on the plan they have selected.

Widgets are useful as they offer tons of information on your dashboard. You can see consumed messages for your consumer or if any consumer’s plan is expiring, you can get to know well in advance. But many times, information overload can affect decision-making. Hence, we have removed non-critical widgets related to consumption levels.

We have made the picture section more noticeable when publishing a new product to Solutions Hub from the Partner Program. The minimum requirements are also adjusted for better appearance.

The Build / Version for hardware on the Publish Product screen is not a mandatory field now.

'Playzone' is now called 'DevLab'. As the name suggests, DevLab acts as a laboratory to learn about the IoTConnect platform. Note that this change across the portal will not affect any functionality of the Partner Program.

'Marketplace' is now called 'Solutions Hub', which is a repository of solutions, hardware and AI models that you can readily use. Note that this change across the portal will not affect any functionality of the Partner Program.

There is no option to upgrade or downgrade a plan anymore. However, plans can be changed from Plans and Packages.

‘Browse AI models’ has replaced the ‘purchase AI models’ button in AI Models module. On clicking, ‘browse AI models,’ you will be redirected to Solution Hub to explore the AI models.

Clicking on ‘Browse AI Models’ will take the partner to Solution Hub, from where they can view the AI models. If any model fulfills their purpose, the partner needs to contact the Avnet Team through the ‘Contact Us’ button on Solution Hub. Avnet’s IoT Partner Program team will then coordinate with the respective partner to create you as consumer in AI products which will enable the consumer to access the AI model.

‘Invitee’ tab is removed from the ‘My Consumers’ module and replaced by create consumer. The former process of creating a consumer through ‘Invitee’ was bit lengthy and little complex too as it was involving a series of emails. Nevertheless, with the current process, a consumer is created just with the click and some minor details. Overall, Partner Program now lets you to create a consumer in hassle-free way.

Using Solution Hub, as a partner, you can extend your customer reach to millions of prospects. During the initial launch of the program, to subscribe or buy your solutions, customers will be required to ‘Contact Us’ from the Partner Program. The Avnet Partner Program team will then contact the respective product owner to create a buyer as a consumer to whom the solution can be sold. This will help the consumers to get access to their requests.

DevLab is now available to everyone. The fundamental idea behind creating DevLab is to allow partners to get familiarized with the IoTConnect platform. Using DevLab, they can simulate the behavior of their products/solutions to address issues before building or launching their application. From now on, DevLab is available to all partners so that they can better explore the potential of IoTConnect.

DevLab messages are available in monthly plans as well. DevLab is the bridge to get more familiarized with IoTConnect. The concern was available messages with DevLab. At first, DevLab was billed annually. But now, that facility has changed with the offering of messages in monthly plans so that users can take more benefits from DevLab.

Earlier, while creating a product, developers were required to create consumers with user APIs. To simplify consumer creation, Partner Program now allows developers to use DevLab as a consumer. With this, there is no need to create a dummy consumer.