25 Posts getaggt mit "dev"

The new API Version allows a, iterative, request chaining mode.

While in the current versions of our API it was already possible to chain requests you can now use iterative and wildcard accessors.

Therefore there are multiple Modes and Options. One can either execute a subrequest for all responses of earlier staged requests

↪ Request

{
    "0": {
        "building_id": 19
    },
    "1": {
        "building_id": 19
    },
    "2": {
        "tag": "$GetBuildingInfo.*.roottag"
    }
}

↩ Response

{
    "GetBuildingInfo": [
        {
            < ... >
        }
    ],
    "GetBuildingInfo": [
        {
            < ... >
        }
    ],
    "LoadTag": [
        {
            < ... >
        }
    ],
    "LoadTag": [
        {
            < ... >
        }
    ]
}

and/or apply the wildcard operator to array data on the response of a function like

$<MethodenName>.<Idx> or <*>.<ParameterName>.<Idx> or <*>.<SubparameterName>.

Here is an example for iterating an array response where three different contagt-IDs loaded from a request result in three resonses for LoadTag.

↪ Request

{
    "0": {
        "building_id": 19
    },
    "1": {
        "tag": "$GetBuildingInfo.0.allTags.*.tag_id"
    }
}

↩ Response

{
    "GetBuildingInfo": [
        {
            < ... >
            allTags: [
                {
                    tag_id: "..."
                },
                {
                    tag_id: "..."
                },
                {
                    tag_id: "..."
                }
            ]
        }
    ],
    "LoadTag": [
        {
            < ... >
        }
    ],
    "LoadTag": [
        {
            < ... >
        }
    ],
    "LoadTag": [
        {
            < ... >
        }
    ]
}

Wildcard request chaining is only functional in strict mode and can lead to undefined behavior sending it on non-strict api calls. You should be very careful with the wildcard feature, since it gets very easy to generate an excessive amount of api load with a single request, especially when using function and parameter wildcards.

Other Changes​

• Rooms and POIs now have a spacial interface allowing to load items more efficiently, especially on large guides.

In Version 1.47.0 it is mainly about caching.

Multiroute Caching​

With this update we introduce the dynamic multi route caching feature which will allow all apps to drastically improve the speed of calculating predefined multiroutes.

This cache does not only improve the reoccuring calculations of entire multiroutes, but also will share equal subroute-caches between multiroutes to reduce the overall expense on cache maintenance.

Exporter Caching​

The Delta-Cache for Exporter Data has been upgraded and is re-enabled within this version. It allows all nativly caching apps to only download the delta-changeset of the the guide data since the last update and will therefore spare some of your prescious traffic volume. At the same time the caching strategies will still be applied to all non-changed data to provide the output to the apps at maximum speed.

Other Changes​

• A new option is made available, that allows the terminal load quicksearch item sizes for the operating user.
• An issue, where the historical movement data would not be loaded correctly from the CE, even when the user is correctly entitled to the asset.

An Hotfix Update has been released, fixing the issue that Webapp loads were not part of the Guide-Access statistics. This is now changed and also affects past entries. All Statistics should now be correct again.

A new Update is available, with the following new features.

• Bumped PHP to the latest Minor Release (8.2.7)
• Accessibility Reporter Admin Interface can now interact with the map in CE.
• News and Info do not export their content in the definitions.
• Campaign-Category templates can be loaded without the campaign for faster suggestions.
• Room and Panorama Images are now part of the Savepoint bundle.

A new Update is available, with the following new features.

• ForceSession SuperUser feature to allow enhancing the default session period.
• Altering Useraccounts as SuperUser will emit warnings for non-changed values.
• Mapfiles can now have more complex roofs on extrusion structures.

Changelog (1.39.X ➔ 1.40.0)​

API Usage​

This update aims for enhanced stability and more unified util interfaces.

The FileController has been enhanced to work with unified rpc requests in the same way as it does with URLEncoded Multipart Fileuploads.

Also it allowes more features for dynamical usage such as receivedFiles to check if the FileController did prepare any uploaded files, accepting an optional parameter to check for a specific transferred file.

Also its usage with internal-api has been simplified and streamlined.

Accessibilty Reporter​

The latest update of the accessibilty reporter allows many new features and bugfixes, that will now allow better administration and preparation of the integration with CE's map.

Changelog (1.38.0 ➔ 1.38.1)​

Routing​

We introduce new intermediate waypoint caching for the routing algorith, that can increase the performance on long and complex routes up to ~8x.

Instead of re-calcuating the distances between nodes in spererate segments, these can now be cached and shared, directly when loading the edge definitons, resul

Also the Viewer for Editor-Sessions was corrected and will show all valid sessions again.

Changelog (1.36.x ➔ 1.37.0)​

With this new Releases, Tags can have a new, optional, setting named showWhileNavigating which can be set to true. If so, these Items (either the Tag's Room or Category Image) should not be hidden while showing any navigation.

Route-Items should be z-indexed higher.

Changelog (1.35.0 ➔ 1.36.0)​

Starting with this Version, the new API Level 19 is introduced, changing structure on the Table tagbase..room_has_content.

There is a new type [field type] called campaign_audio. This type has a special, breaking behavior. It does not implement any actual data, but the field displayname contains the Id if the actual campaign this content should be replaced by.

Therefore the Apps shall display an Audio-Player for this (just like in the Campaigns) playing the defined campagins contents.

To support the migration, the API_STRUCTURE_VERSION will be incremented to 18.

Beginning with the (now releases) Version the Method BoundingBox#extendMargin of VTM was corrected in its behavior.

From now on, it exposes three overloads:

BoundingBox extendMargin(float margin) 

BoundingBox extendMargin(float marginX, float marginY) 

BoundingBox extendMargin(float marginLeft, float marginRight, float marginTop, float marginBottom)

for a better and more dynamic usage of this feature.

Also the value margin was changed from maximum randomness in behavior (it was a factor that was somehow based on the original boundingbox, but not really undestandable) to percent. So extendMargin(50) will extend the original BoundingBox by 50% of its original size into all directions.

Also it now accepts negative values to shrink the orignal Box.

For further details click here.