Class lispa\amos\partnershipprofiles\models\PartnershipProfiles

Override for demos

The default implementation will trigger an EVENT_BEFORE_INSERT event when $insert is true, or an EVENT_BEFORE_UPDATE event if $insert is false. When overriding this method, make sure you call the parent implementation like the following:

public function beforeSave($insert)
{
    if (!parent::beforeSave($insert)) {
        return false;
    }

    // ...custom code here...
    return true;
}

This method verify if it's possible to make an expression of interest on this partnership profile.

The community created by the context model (community related to project-management, events or a community itself)

This method return the expired date.

Getter for $this->partnershipProfileAttachments;

This method return a string with all the partnership profile types concatenated with commas.

Useful in grid view or similar places.

Return the publicated at property label

Return the publicated from property label

Return the translated status label

For this entity the validation logic is different from lispa\amos\core\record\Record The facilitator is linked to this "partnership profile"

This method checks if this partnership profile is expired.

It uses the calculated expiry date and the actual date to do the check.

Returns a list of scenarios and the corresponding active attributes.

An active attribute is one that is subject to validation in the current scenario. The returned array should be in the following format:

[
    'scenario1' => ['attribute11', 'attribute12', ...],
    'scenario2' => ['attribute21', 'attribute22', ...],
    ...
]

By default, an active attribute is considered safe and can be massively assigned. If an attribute should NOT be massively assigned (thus considered unsafe), please prefix the attribute with an exclamation character (e.g. '!rank').

The default implementation of this method will return all scenarios found in the rules() declaration. A special scenario named SCENARIO_DEFAULT will contain all attributes found in the rules(). Each scenario will be associated with the attributes that are being validated by the validation rules that apply to the scenario.