...
Expand | ||
---|---|---|
| ||
|
Version 2.0.37
- Fixed issue with restricted fields shown when a view is used with a filter macro
- ConfiForms now exposes a component class (com.vertuna.confluence.plugins.confiforms.api.ConfiFormsStorageComponent) for plugin-to-plugin integrations with the following API
Code Block |
---|
@ExportAsService({ConfiFormsStorageComponent.class})
@Named("confiFormsStorageComponent") |
Code Block |
---|
public interface ConfiFormsStorageComponent {
String findFieldValueById(ContentEntityObject contentEntityObject, String formName, String id, String fieldName);
RegEntry findById(ContentEntityObject contentEntityObject, String formName, String id);
List<RegEntry> findByAll(ContentEntityObject contentEntityObject, String formName);
List<RegEntry> findRecordsByCurrentUser(ContentEntityObject contentEntityObject, String formName);
List<RegEntry> findRecordsByUser(ContentEntityObject contentEntityObject, String formName, String username);
void updateField(ContentEntityObject contentEntityObject, String formName, String query, String field, String value) throws Exception;
} |
- Fixed issue with showing pages (multi-page field) when referenced through a smart field
- Fixed issue with "web service request" IFTTT action not respecting the "silent" parameter
- asLink function now supports setting up the parameter via entry field's reference, [entry.field_name]
- Fixed issue with "web service request" IFTTT action when 204 is returned (NPE when reading response stream, which is totally incorrect in case of NoContent response)
- String matching is now case sensitive in filters!
Version 2.0.36
- Hotfix to address issue with formula value rendering when recalculation is not needed
...